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
+14-11Lines changed: 14 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,18 @@
1
-
1.11.1 (December XX, 2023)
2
-
- Bugfixing - Fixed manager methods in consumer modes to return results in a promise when the SDK is not operational (not ready or destroyed).
1
+
1.12.0 (December 4, 2023)
2
+
- Added support for Flag Sets in "consumer" and "partial consumer" modes for Pluggable and Redis storages.
3
+
- Updated evaluation flow to log a warning when using flag sets that don't contain cached feature flags.
4
+
- Updated Redis adapter to handle timeouts and queueing of some missing commands: 'hincrby', 'popNRaw', and 'pipeline.exec'.
5
+
- Bugfixing - Fixed manager methods in consumer modes to return results in a promise when the SDK is not operational (not ready or destroyed).
3
6
4
7
1.11.0 (November 3, 2023)
5
-
- 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):
6
-
- Added new variations of the get treatment methods to support evaluating flags in given flag set/s.
7
-
- getTreatmentsByFlagSet and getTreatmentsByFlagSets
8
-
- getTreatmentsWithConfigByFlagSets and getTreatmentsWithConfigByFlagSets
9
-
- 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.
10
-
- 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.
11
-
- 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.
12
-
- 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).
8
+
- 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):
9
+
- Added new variations of the get treatment methods to support evaluating flags in given flag set/s.
10
+
- getTreatmentsByFlagSet and getTreatmentsByFlagSets
11
+
- getTreatmentsWithConfigByFlagSets and getTreatmentsWithConfigByFlagSets
12
+
- 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.
13
+
- 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.
14
+
- 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.
15
+
- 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).
13
16
14
17
1.10.0 (October 20, 2023)
15
18
- 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).
@@ -56,7 +59,7 @@
56
59
- Added a new impressions mode for the SDK called NONE, to be used in factory when there is no desire to capture impressions on an SDK factory to feed Split's analytics engine. Running NONE mode, the SDK will only capture unique keys evaluated for a particular feature flag instead of full blown impressions.
57
60
- Updated SDK telemetry to support pluggable storage, partial consumer mode, and synchronizer.
58
61
- Updated storage implementations to improve the performance of feature flag evaluations (i.e., `getTreatment(s)` method calls) when using the default storage in memory.
59
-
- Updated evaluation flow to avoid unnecessarily storage calls when the SDK is not ready.
62
+
- Updated evaluation flow (i.e., `getTreatment(s)` method calls) to avoid calling the storage for cached feature flags when the SDK is not ready or ready from cache. It applies to all SDK modes.
60
63
61
64
1.6.1 (July 22, 2022)
62
65
- Updated GoogleAnalyticsToSplit integration to validate `autoRequire` config parameter and avoid some wrong warning logs when mapping GA hit fields to Split event properties.
@@ -123,7 +116,7 @@ test('EVALUATOR - Multiple evaluations at once / should return right labels, tre
123
116
124
117
});
125
118
126
-
test('EVALUATOR - Multiple evaluations at once by flag sets / should return right labels, treatments and configs if storage returns without errors.',asyncfunction(){
119
+
describe('EVALUATOR - Multiple evaluations at once by flag sets',()=>{
127
120
128
121
constexpectedOutput={
129
122
config: {
@@ -135,44 +128,76 @@ test('EVALUATOR - Multiple evaluations at once by flag sets / should return righ
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.
expect(multipleEvaluationAtOnceByFlagSets['config']).toEqual(expectedOutput['config']);// If the split is retrieved successfully we should get the right evaluation result, label and config.
148
+
// @todo assert flag set not found - for input validations
149
+
150
+
// assert regular
151
+
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.WARN_NOT_EXISTENT_SPLIT,'%s: feature flag "%s" does not exist in this environment. Please double check what feature flags exist in the Split user interface.'],
25
25
[c.WARN_LOWERCASE_TRAFFIC_TYPE,'%s: traffic_type_name should be all lowercase - converting string to lowercase.'],
26
26
[c.WARN_NOT_EXISTENT_TT,'%s: traffic type "%s" does not have any corresponding feature flag in this environment, make sure you\'re tracking your events to a valid traffic type defined in the Split user interface.'],
27
-
[c.WARN_FLAGSET_NOT_CONFIGURED,'%s: : you passed %s wich is not part of the configured FlagSetsFilter, ignoring Flag Set.'],
27
+
[c.WARN_FLAGSET_NOT_CONFIGURED,'%s: you passed %s which is not part of the configured FlagSetsFilter, ignoring Flag Set.'],
28
28
// initialization / settings validation
29
-
[c.WARN_INTEGRATION_INVALID,c.LOG_PREFIX_SETTINGS+': %s integration item(s) at settings is invalid. %s'],
30
-
[c.WARN_SPLITS_FILTER_INVALID,c.LOG_PREFIX_SETTINGS+': feature flag filter at position %s is invalid. It must be an object with a valid filter type ("bySet", "byName" or "byPrefix") and a list of "values".'],
31
-
[c.WARN_SPLITS_FILTER_EMPTY,c.LOG_PREFIX_SETTINGS+': feature flag filter configuration must be a non-empty array of filter objects.'],
32
-
[c.WARN_SDK_KEY,c.LOG_PREFIX_SETTINGS+': You already have %s. We recommend keeping only one instance of the factory at all times (Singleton pattern) and reusing it throughout your application'],
29
+
[c.WARN_INTEGRATION_INVALID,c.LOG_PREFIX_SETTINGS+': %s integration item(s) at settings is invalid. %s'],
30
+
[c.WARN_SPLITS_FILTER_IGNORED,c.LOG_PREFIX_SETTINGS+': feature flag filters are not applicable for Consumer modes where the SDK does not keep rollout data in sync. Filters were discarded'],
31
+
[c.WARN_SPLITS_FILTER_INVALID,c.LOG_PREFIX_SETTINGS+': feature flag filter at position %s is invalid. It must be an object with a valid filter type ("bySet", "byName" or "byPrefix") and a list of "values".'],
32
+
[c.WARN_SPLITS_FILTER_EMPTY,c.LOG_PREFIX_SETTINGS+': feature flag filter configuration must be a non-empty array of filter objects.'],
33
+
[c.WARN_SDK_KEY,c.LOG_PREFIX_SETTINGS+': You already have %s. We recommend keeping only one instance of the factory at all times (Singleton pattern) and reusing it throughout your application'],
33
34
34
35
[c.STREAMING_PARSING_MY_SEGMENTS_UPDATE_V2,c.LOG_PREFIX_SYNC_STREAMING+'Fetching MySegments due to an error processing %s notification: %s'],
35
36
[c.STREAMING_PARSING_SPLIT_UPDATE,c.LOG_PREFIX_SYNC_STREAMING+'Fetching SplitChanges due to an error processing SPLIT_UPDATE notification: %s'],
36
-
[c.WARN_SPLITS_FILTER_INVALID_SET,c.LOG_PREFIX_SETTINGS+': you passed %s, flag set must adhere to the regular expressions %s. This means a flag set must start with a letter or number, be in lowercase, alphanumeric and have a max length of 50 characters. %s was discarded.'],
37
-
[c.WARN_SPLITS_FILTER_LOWERCASE_SET,c.LOG_PREFIX_SETTINGS+': flag set %s should be all lowercase - converting string to lowercase.'],
37
+
[c.WARN_SPLITS_FILTER_INVALID_SET,c.LOG_PREFIX_SETTINGS+': you passed %s, flag set must adhere to the regular expressions %s. This means a flag set must start with a letter or number, be in lowercase, alphanumeric and have a max length of 50 characters. %s was discarded.'],
38
+
[c.WARN_SPLITS_FILTER_LOWERCASE_SET,c.LOG_PREFIX_SETTINGS+': flag set %s should be all lowercase - converting string to lowercase.'],
39
+
[c.WARN_FLAGSET_WITHOUT_FLAGS,'%s: you passed %s flag set that does not contain cached feature flag names. Please double check what flag sets are in use in the Split user interface.'],
0 commit comments