Must select value type of new feature instead of defaulting to Boolean #2553
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jdorn
changed the title
|
Your preview environment pr-2553-bttf has been deployed. Preview environment endpoints are available at: |
Auz
approved these changes
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Features and Changes
When creating a new feature, we now require you to select the value type instead of defaulting to Boolean.
This addresses an issue where users mistakenly create Boolean flags for things they meant to be strings/json. By forcing people to make a choice, we hope to reduce these accidents.
This PR also re-orders the value type options. It now goes Boolean -> String -> Number -> JSON
New default modal view: