-
Notifications
You must be signed in to change notification settings - Fork 3.1k
docs(input-otp): add documentation for new input-otp component #4112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: feature-8.6
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most are suggestions/questions. I would like to see the code to be on newlines though.
The component supports various states for automatic styling of input boxes: | ||
- `disabled` and `readonly` states via respective properties | ||
- Form validation states: `valid` and `invalid` visually indicated through CSS classes | ||
- In Angular: validation states are automatically managed through the framework's value accessors and form validation | ||
- For other frameworks: developers must manually add `ion-valid`, `ion-invalid`, and `ion-touched` classes | ||
- `ion-invalid` styles only display when touched (`ion-touched`) | ||
- `ion-valid` styles only display when focused (`has-focus`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also update the other input pages to reflect this (in another PR).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Adds documentation & playgrounds for the new
ion-input-otp
component.Preview