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.
Hi there! 👋
I’m the developer of [Wandry UI](http://ui.wandry.com.ua/) — a shadcn registry collection of fully controlled form components.
I’d like to suggest integrating it into the starter kit.
Here’s why it could be beneficial:
Much less boilerplate code.
For example, instead of writing something like this:
You can simply use the component:
Built-in state management.
Components automatically handle
setValueinternally, so you don’t need to manage form state manually.Global access to form values.
You can access form values from any child component.
For example, if you want to create an AddressField component that updates the list of cities based on the selected country, you can do:
Built-in SubmitButton.
It already includes loading,
disabled, andtype="submit"handling — just drop it in and it works out of the box.Automatic error handling.
Validation errors returned from the backend are automatically displayed under the corresponding fields.
Field and error reset support.
I’ve refactored all existing forms using wandry-ui and @wandry/inertia-form.
@taylorotwell, @joetannenbaum, @hugosaintemarie, Would love to hear your thoughts on this!