canSubmit is true when the form is touched but an invalid onChange field is not touched
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.7k
- Forks
- 682
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 7
Description
Describe the bug
According to the docs, "canSubmit is true until the form has been touched, even if some fields are "technically" invalid based on their onChange/onBlur props". As far as I understand, field-level validations will only change canSubmit when that field has been touched, whereas form-level validations will affect canSubmit when any field has been touched. It would be helpful if this distinction could be made clear in the docs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the documentation for canSubmit, especially the sections describing onChange/onBlur validation and touched fields. Clarify how field-level and form-level validations affect canSubmit, and consider the work done when the documented distinction matches the behavior described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100