Releases: configcat/react-sdk
Releases · configcat/react-sdk
v4.8.1
v4.8.0
v4.7.0
v4.6.1
Improvements:
- Make the timing of polling iterations more accurate in Auto Polling mode. (configcat/common-js#106)
Bug fixes:
- Check cache expiration in every poll iteration, not just the first one in Auto Polling mode to reduce network traffic when the SDK uses a shared cache (including LocalStorage cache used by instances of a browser app running in multiple browser tabs). (configcat/common-js#106)
- Synchronize in-memory cache with the external cache in every poll iteration, not just the first one in Auto Polling mode regardless of offline mode to keep in-memory cache up-to-date when the SDK uses a shared cache.
- Protect poll iterations with try-catch so a potential exception doesn't stop the polling loop in Auto Polling mode.
v4.6.0
v4.5.0
v4.4.0
Improvements:
- Make naming of
UserComparator
members consistent. (configcat/common-js#102) - Make line terminator character sequence configurable in log messages.
- Adjust the terminology used in JSDoc comments to the main documentation.
- Minor performance improvements.
Bug fixes:
- Align evaluation logging and evaluator error reporting in some edge cases where the config JSON contains errors.
- Correct grammar mistakes in error messages.
Breaking changes:
- Change the name of some
UserComparator
members:Is(Not)OneOf
->TextIs(Not)OneOf
,SensitiveIs(Not)OneOf
->SensitiveTextIs(Not)OneOf
,(Not)ContainsAnyOf
->Text(Not)ContainsAnyOf
. (Low impact expected.)
v4.3.0
New features/improvements:
- Add an optional parameter named
watchChanges
tocreateFlagOverridesFromMap
which controls whether the client should detect changes to the flag override map after client initialization. (configcat/common-js#101)
Bug fixes:
- Reference a fixed version of
configcat-common
to avoid issues in case the "pubternal" API ofconfigcat-common
changes. (#48)
v4.2.0
Improvements:
- Upgrade to configcat-common v9.1.0.
- Send ETag as a query string parameter when running in browser (because browsers don't send it automatically in every case).
- Upon client initialization test for the availability of the local storage and use
LocalStorageCache
only if it's available. Otherwise, use the default (in-memory) cache implementation. - Don't swallow exceptions which are thrown in the
LocalStorageCache.get
/set
methods so the outer exception handlers can catch and log them.
v4.1.0
Fixed a cache issue with non Latin 1 characters in the config.json.