Form validation pattern
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 79
- Forks
- 52
- Avg merge
- 18h 58m
- Merged PRs (30d)
- 4
Description
Summary
Pattern for conducting validation of data including input validation and form validation.
💬 Description
Additional examples and improvements to the form validation patterns on the design system website.
Consider common error and warning types including connectivity failure, systems offline, extreme data scenarios (too big too small), required fields missing.
Detail custom validation methods.
Consider inline field validation as well as default field validation.
💰 Use value
Additional and/or improved examples of form validation will allow developers to gain a better understanding of what their own implementations should achieve.
Additional info
Related stories
#188
#189
#222
#203
https://github.com/mi6/ic-ui-kit/issues/465
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 reviewing the existing form validation patterns on the design system website and the related issues #188, #222, #203, and #465. Expand the examples to cover connectivity failures, offline systems, extreme values, missing required fields, custom validation, and both inline and default field validation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100