Allow arbitrary keys for form components - #463
Merged
Merged
Conversation
Sometimes one needs arbitrary keys for front-end only components or perhaps other creative uses. This change allows that while preserving the ability to select from mapped keys and validate them. In the future we may want to add some sort of feature to ensure that arbitrary keys are only used when you explicitly want them... or just make the validation more readily apparent, perhaps by color coding components that are mapped vs. arbitrary? closes #369
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Sometimes one needs arbitrary keys for front-end only components or
perhaps other creative uses.
This change allows that while preserving the ability to select from
mapped keys and validate them.
In the future we may want to add some sort of feature to ensure that
arbitrary keys are only used when you explicitly want them... or just
make the validation more readily apparent, perhaps by color coding
components that are mapped vs. arbitrary?
closes #369
screenrecording-2026-08-20_17-26-09.mp4