dart-sdk

Fixed

• Initial config JSON load when auto poll enabled with results from cache.

Changed

• Rename SettingsValue to correct SettingValue
• Add getKeyAndValue missing exception
• Improve prerequisite flag evaluation type checks
• Typo fixes

Fixed

• WEB platform support.

Changed

• In the case of WEB platform, the SDK now sends the ETag and the SDK-related info in query parameters.

New features and improvements

• Add support for the new Config JSON v6 format: update the config model and implement new features in setting evaluation logic.
• Overhaul setting evaluation-related logging and make it consistent across SDKs.
• SDK key format validation (when client is not set up to use local-only flag overrides).
• Go to the cache in all polling modes instead of using the in memory variable.

Breaking changes

• Change the ConfigCatUser constructor custom parameter type to Map<String, Object> to allow other values than string.
• Rename the matchedEvaluationRule property to matchedTargetingRule and the matchedEvaluationPercentageRule property to matchedPercentageOption in EvaluationDetails.
• Change Config model

Changed

• Standardized config cache key generation algorithm and cache payload format to allow shared caches to be used by SDKs of different platforms.

Removed

• getVariationId() / getAllVariationIds() methods. Alternative: getValueDetails() / getAllValueDetails()

Removed

• logger package dependency. Switched to simple print() as default.

Changed

• Bump to dio v5.2.0 in order to use DioException instead of the deprecated DioError.

Changed

• Bumped dependency versions.
• Set min Dart SDK version to >=2.19.0.

Added

• New getAllValueDetails() method.

Changed

• Deprecated getVariationId() and getAllVariationIds() methods in favor of getValueDetails() and getAllValueDetails().

Changed

• Renamed mode configuration option to pollingMode.

Fixed

• Prevent auto-poll from starting when the SDK is initialized in offline mode.

Added

• Allow offline SDK initialization with an offline configuration option.

Changed

• RolloutPercentageItem -> PercentageRule

Fixed

• Set the user field of EvaluationDetails in case of errors.

Fixed

• Hanging due to non-cancelled Future.delayed.

Fixed

• Static analyzer warnings.

Added

• setDefaultUser(user) / clearDefaultUser() methods to set / remove a default user object used when there's no user passed to getValue() / getValueDetails() / getAllValues() / getAllVariationIds() methods.
• setOffline() / setOnline() methods to indicate whether the SDK is allowed to make HTTP calls or not. In 'offline' mode the SDK works from the cache only.
• onClientReady() / onConfigChanged(Map<string, Setting>) / onFlagEvaluated(EvaluationDetails) / onError(String) hooks. Subscription is possible on client initialization options and on the hooks property of ConfigCatClient.
• getValueDetails() method to retrieve evaluation details along with the feature flag / setting value. It returns the same details that is passed to onFlagEvaluated(EvaluationDetails) on each evaluation.

Changed

• The static close() method was split to an instance level close() method which closes the given ConfigCatClient and to a static closeAll() method which closes all instantiated client instances.
• The forceRefresh() method now returns with a result object that indicates whether the refresh succeeded or not.
• The TTL of lazyLoad and interval of autoPoll is compared against a cached fetchTime, which allows the SDK not necessarily download a new config.json at each application restart.

Removed

• The onConfigChanged() hook parameter of PollingModes.autoPoll(). It was replaced by the newly introduced onConfigChanged(Map<string, Setting>) hook function which is invoked with each polling mode.

Changed

• Replaced the refresh policies construction with a single config service that takes care of the different polling mechanisms, caching, and the synchronization of HTTP requests.

Fixed

• Send the correct SDK version in HTTP header.

Fixed

• When the dataGovernance parameter wasn't in match with the remote setting, it could have happened that the fetcher downloaded the correct config.json multiple times.

• First official release.