New form system #453
Open
New form system #453
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
This PR is a second attempt at a new form system to replace the old, redux-form, based approach.
<Form>component, supporting async onSubmit handler<Field>component, which connects any standard or custom input to the form system. When rendered within<Form />automatically handles registering/unregistering.<FieldSet />component, designed for grouping<Field />components, and conditionally rendering them.useForm,useField, anduseFormValuehooks to enable clean composition patterns, and features such as conditional renderinguseProtocolFormcustom hook, which translates a protocol form definition to a renderable list ofFieldcomponents.