Releases: configcat/swift-sdk
Releases · configcat/swift-sdk
v8.0.0
Fixed
- During an ongoing fetch, all additional fetch requests will be waiting for the ongoing fetch's result.
- JSON deserialization happens only when the actual JSON differs from the cached one in memory.
- The evaluation logs are staying on the info level but they are now combined into a single log entry.
- Remove the default
inMemoryConfigCache
to keep only a single Config instance in memory at once.
Added
- A
getAllValues()
function was added that evaluates all flags & settings in a[String: Any]
. - New
flagOverrides
parameter to support the reading of flags & settings from a[String: Any]
.
Breaking Changes
maxWaitTimeForSyncCallsInSeconds
was replaced withmaxInitWaitTimeInSeconds
in case of the auto poll to give a maximum amount of wait time for the first config JSON fetch. When it's reached without a result, the latest cached value will be returned.
v7.2.1
v7.2.0
v7.1.0
v7.0.0
v6.0.0
Addressing global data handling and processing trends via Data Governance feature. Customers can control the geographic location where their config JSONs get published to. See the docs.
We are introducing a new DataGovernance initialization parameter. Set this parameter to be in sync with the Data Governance preference on the Dashboard.
Breaking change:
- Custom cache implementations should implement the new cache interface using key parameter in the get/set methods.
ConfigCat Swift SDK v5.1.0
Added variation id related functions to support integration with analytical tools:
getVariationId[Async]()
getAllVariationIds[Async]()
getKeyAndValue[Async]()
Removed case-insensitive attribute key support.
ConfigCat Swift SDK v5.0.1
Breaking change: Renamed API Key
to SDK Key
.
ConfigCat Swift SDK v4.0.0
Supporting sensitive text comparators.
ConfigCat Swift SDK v3.1.0
- Changed the on configuration changed event. See more.