feat: support form submission via FormData #2324
Draft
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 is a proposed improvement to simplify form input handling with minimal abstraction.
I'm creating this as a draft because I don't think it's necessarily dogmatic but I see it as an improvement.
After attending Leah's Inertia.js talk at React Miami, I found myself thinking the form input handling was a bit too verbose for some use cases. Currently, forms require individual
onChange
events for every input (updating the component state), which feels like it can be unnecessarily complex for some use-cases.This PR adds the ability to pass the form element (target) as an option to the
form.post
method, which will then use nativeFormData
to handle the payload.For example:
While this pattern might not be used everywhere, I believe it's valuable to offer a more native, standards-focused API for use-cases that require minimal abstraction.