Releases: cap-js-community/feature-toggle-library
v1.0.0
We are releasing 1.0, after 2 years of continuous usage, testing, and small improvements.
Removed
- restrict to node v18+
Added
- act as Feature Vector Provider when used as a CDS-plugin.
- allow graceful shutdown by closing redis clients on cds shutdown event (fixes #34).
v0.7.2
Added
- support for redis cluster configurations.
- enable setting maximal log level through env variable
BTP_FEATURES_LOG_LEVEL
. this can be used to silence the
library during tests.
Changed
- implement new cds-plugin API, where plugins export a promise instead of an activate property and stay compatible for
older cds versions.
v0.7.1
Fixed
- cds-plugin integration now works for projects that run
cds build --production
and only use the resulting
csn.json
at runtime.
v0.7.0
Added
-
new harmonized validation configuration for scope and regex checks, as well as external validation with user
provided modules. -
new (optional) cds-plugin integration. for details, see the new
plugin and service documentation. -
new logger implementation which replaces
cf-nodejs-logging-support dependency. it has better cds
integration (if present). for example, it will log
correlation ids that are present in cds
context via async local storage.
Changed
-
allowedScopes: [xxx]
configuration will now be ignored and needs to be replaced with
validations: [{ scopes: [xxx] }]
. -
validation: yyy
configuration will now be ignored and needs to be replaced with
validations: [{ regex: yyy }]
.
Fixed
- re-work pipelines to separate main branch and pr-voter status
v0.6.9
Added
- example http request file for example-cap-server
Fixed
-
better documentation regarding scoping and redis hash map persistence
-
more resilient handling of bad input for scopeMaps in all external APIs