feat: form v2 and inputs v2 #105
Merged
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
|
🎉 This PR is included in version 3.1.0-beta.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Oct 8, 2024
|
🎉 This PR is included in version 3.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Form and input components V2!
Background
Formis no longer flexible enough to handle all of the cases we want it to.FormV2solves for this by splitting components out and expecting them to be rendered separately, allowing for more flexibility in how we render and style inputs in consuming components.Description
FormV2and deprecatesForm.InputText,InputCheckbox, and an improvedInputPasswordcomponentAcceptance Criteria
/form-v2-demo