fix(deps): update dependency flagsmith to v7 #1082
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.0.0
->^7.0.0
4.0.0
->7.0.1
Release Notes
Flagsmith/flagsmith-js-client (flagsmith)
v7.0.1
: Version 7.0.1Compare Source
Allows
flagsmith.setContext({...})
prior to init.v7.0.0
Compare Source
This is a temporary release that reverts the changes in 6.0.0.
What's Changed
Full Changelog: Flagsmith/flagsmith-js-client@6.0.0...7.0.0
v6.0.0
: Version 6.0.0 - Adjust cache keys to be unique per environmentCompare Source
Closes #201. The local storage keys for the SDK cache are now unique for each environment. This is being released as a breaking change because, upon upgrading to this version, the cache will be missed the first time due to the previous key ('BULLET_TRAIN_DB') being ignored
Thank you very much for the great PR @oluizcarvalho 🚀
v5.0.0
: Version 5.0.0 - Support context, transient identities and traitsCompare Source
Transient traits
This release supports the concept of transient traits, setting this will mean the trait is not stored within Flagsmith and evaluated just in that request.
You can define a trait as transient like so:
Contexts and transient identities
This release also deprecates the above calls in favour of setting context. Context allows you to set information as a single object which we may extend in future more easily. We suggest migrating to this soon.
You can set a partial context and it will merge with the one provided during SDK init.
Currently, the full context object looks like this:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.