This repository was archived by the owner on May 30, 2024. It is now read-only.
Add in memory dev data store as a configuration option. This allows u… #166
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.
…sers to pass in small features for evaluation locally without having to connect to Launch Darkly services. This also allows easy "pull and play" configurations
Requirements
Related issues
N/A
Describe the solution you've provided
This allows a configuration option for feature flags to be evaluated offline in the update processor.
Describe alternatives you've considered
In-theory, you could select offline mode and provide an SDK key and file to evaluate, but this gets messy across large distributed teams. This allows us to have one LaunchDarkly config that can be easily changed across branches.
Additional context
For our release cycles, it became hard to manage multiple flags, files, and configs. This unifies configuration into the LD configuration and allows new members to pull projects and easily implement local feature flags server-side.