chore(docs): splitting out "stable" feature flags by intent (config vs feature dev) #28016
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.
SUMMARY
There was some discussion in Town Hall about whether or not we should use feature flags for runtime configuration or not. The jury is still out! No matter where they live, I figured that at least for now, we should split these up by intent. Then it's clearer to users whether these "stable" flags are ones that will remain (for now, anyway) as config, vs the ones that will march toward feature release and flag deprecation.
If this makes sense as a small intermediary step, let me know if I've miscategorized any of them :)
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION