Introduce experimental features section in Settings #837
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 gives us a tool to rollout features that we want to get feedback on before releasing them.
At the same time as it gives users a list of available experimental features to chose from, users understand that they're experimental and can break at any time.
Users toggle the experimental features from the Settings sidebar, at the bottom.
With this PR it's hidden because there are no features to toggle.
Also note that to be able to persist the users settings we store this in the users local storage. However, men we move a feature off of the experimental list, it will still show up in users Settings sidebar if we don't check what should be there.
That's the reason for the
cherrypickAndMergefunction in the experimental feature duck file.This is what it looks like with a feature added:

To try manually, add this to the
initialStateof the experimental features reducer:btw, the experimental features section in the Settings panel is feature toggled by the default entry. Non visible to change for the users though, but you can toggle it via local storage.