Form should accept all form props
See original GitHub issueI need to be able to apply className
and action
in some cases; it’d be convenient for the form to accept all the props that a form can accept.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Forms - React
Specifying the value prop on a controlled component prevents the user from changing the input unless you desire so. If you've specified a...
Read more >The Form element - HTML: HyperText Markup Language | MDN
The HTML element represents a document section containing interactive controls for submitting information.
Read more ><Form /> props - react-jsonschema-form documentation
The value of this prop will be passed to the accept-charset HTML attribute on the form. action¶. The value of this prop will...
Read more >Working with Forms in React - SitePoint
This article will walk you through the basics of using forms in React to allow users to add or edit information. We'll look...
Read more >BEST Ways to Handle and Validate React Forms without a ...
React form validation tutorial. How to handle and validate React form inputs using different ways. Handling forms in React using useState, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve published this as a minor, and it’s available under 1.1.0. I don’t think it makes sense to publish 2.0 after only 3 days of existence 😅
The minor is as per semantic version prescribes.
This will be the only time that I’ll introduce a breaking change like this. But because we are 3 days old and have under 200 installs @ npm, I think it’s okay(ish) for now.
I looked back at the form code, and I see there’s already
onSuccess
andonError
, so I think calling the user’sonSubmit
on submit start would make sense. They might need the event for whatever reason ¯\_(ツ)_/¯On an unrelated note, I’m enjoying this library a lot so far 😄