[2.12.4] - 2019-07-10
Changed:
- The
useReport
property, which tells the SDK to use the REPORT method for HTTP requests so that user data will not appear in the URL path, was only actually using REPORT for requesting all flags at once— not for streaming updates, because streaming uses the EventSource API which normally can only use the GET method; so, to avoid exposing user data in the URL for the streaming connection, the SDK had to use a different and slower mechanism (in which all of the flags are reloaded whenever there is a change) ifuseReport
was true. That is still the case by default; but, if you load the specific EventSource polyfill implementationlaunchdarkly-eventsource
(v1.1.0 or later), the SDK can now use REPORT for streaming connections.
Fixed:
- The
homepage
attribute in thelaunchdarkly-react-client-sdk
andlaunchdarkly-react-client-sdk-example
packages has been updated to the correct value.