-
Notifications
You must be signed in to change notification settings - Fork 3.2k
docs(input): removed mentions of legacy syntax support for ion-input #4202
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: main
Are you sure you want to change the base?
docs(input): removed mentions of legacy syntax support for ion-input #4202
Conversation
@kkindrai is attempting to deploy a commit to the Ionic Team on Vercel. A member of the Team first needs to authorize it. |
@@ -192,7 +192,7 @@ import CSSProps from '@site/static/usage/v8/input/theming/css-properties/index.m | |||
|
|||
A simpler input syntax was introduced in Ionic 7.0. This new syntax reduces the boilerplate required to setup an input, resolves accessibility issues, and improves the developer experience. | |||
|
|||
Developers can perform this migration one input at a time. While developers can continue using the legacy syntax, we recommend migrating as soon as possible. | |||
Developers can perform this migration one input at a time. The legacy syntax is no longer supported. |
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.
kkindrai Maybe something like
Developers can migrate inputs individually, as the legacy syntax is now deprecated and no longer supported.
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.
@gnbm The legacy syntax isn't deprecated in v8 it was completely removed.
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.
We should remove the entire Migrating from Legacy Input Syntax
section since the legacy syntax was removed in v8. We can leave the section in v7.
Also, are we planning on separate PRs for the other components (textarea, select, etc)?
Thank you!
Resolves #4057
Using Legacy Support Syntax
Migrating from Legacy Syntax
to remove mention of Legacy still being supported