You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGES.txt
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,13 @@
1
+
1.11.0 (November 3, 2023)
2
+
- Added support for Flag Sets on the SDK, which enables grouping feature flags and interacting with the group rather than individually (more details in our documentation):
3
+
- Added new variations of the get treatment methods to support evaluating flags in given flag set/s.
4
+
- getTreatmentsByFlagSet and getTreatmentsByFlagSets
5
+
- getTreatmentsWithConfigByFlagSets and getTreatmentsWithConfigByFlagSets
6
+
- Added a new optional Split Filter configuration option. This allows the SDK and Split services to only synchronize the flags in the specified flag sets, avoiding unused or unwanted flags from being synced on the SDK instance, bringing all the benefits from a reduced payload.
7
+
- Note: Only applicable when the SDK is in charge of the rollout data synchronization. When not applicable, the SDK will log a warning on init.
8
+
- Added `sets` property to the `SplitView` object returned by the `split` and `splits` methods of the SDK manager to expose flag sets on flag views.
9
+
- Bugfixing - Fixed SDK key validation in NodeJS to ensure the SDK_READY_TIMED_OUT event is emitted when a client-side type SDK key is provided instead of a server-side one (Related to issue https://github.com/splitio/javascript-client/issues/768).
10
+
1
11
1.10.0 (October 20, 2023)
2
12
- Added `defaultTreatment` property to the `SplitView` object returned by the `split` and `splits` methods of the SDK manager (Related to issue https://github.com/splitio/javascript-commons/issues/225).
3
13
- Updated log warning message to include the feature flag name when `getTreatment` method is called and the SDK client is not ready.
@@ -105,3 +122,57 @@ test('EVALUATOR - Multiple evaluations at once / should return right labels, tre
105
122
// If the split is retrieved but is not in split (out of Traffic Allocation), we should get the right evaluation result, label and config.
106
123
107
124
});
125
+
126
+
test('EVALUATOR - Multiple evaluations at once by flag sets / should return right labels, treatments and configs if storage returns without errors.',asyncfunction(){
expect(multipleEvaluationAtOnceByFlagSets['config']).toEqual(expectedOutput['config']);// If the split is retrieved successfully we should get the right evaluation result, label and config.
154
+
// @todo assert flag set not found - for input validations
155
+
156
+
// assert regular
157
+
expect(multipleEvaluationAtOnceByFlagSets['regular']).toEqual({ ...expectedOutput['config'],config: null});// If the split is retrieved successfully we should get the right evaluation result, label and config. If Split has no config it should have config equal null.
[c.ERROR_LOCALHOST_MODULE_REQUIRED,c.LOG_PREFIX_SETTINGS+': an invalid value was received for "sync.localhostMode" config. A valid entity should be provided for localhost mode.'],
35
35
[c.ERROR_STORAGE_INVALID,c.LOG_PREFIX_SETTINGS+': the provided storage is invalid.%s Falling back into default MEMORY storage'],
36
36
[c.ERROR_MIN_CONFIG_PARAM,c.LOG_PREFIX_SETTINGS+': the provided "%s" config param is lower than allowed. Setting to the minimum value %s seconds'],
37
+
[c.ERROR_TOO_MANY_SETS,c.LOG_PREFIX_SETTINGS+': the amount of flag sets provided are big causing uri length error.'],
38
+
[c.ERROR_SETS_FILTER_EXCLUSIVE,c.LOG_PREFIX_SETTINGS+': the Set filter is exclusive and cannot be used simultaneously with names or prefix filters. Ignoring names and prefixes.'],
0 commit comments