-
Notifications
You must be signed in to change notification settings - Fork 13
refactor(form): make errrormessageid required #1365
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?
Conversation
Summary of ChangesHello @akashsonune, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a breaking change by making the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request makes the errormessageId property on the SiFormItemControl interface required, which is a breaking change. This is a good step towards improving accessibility for form error messages. The change is correctly implemented in SiFormlyFormFieldProviderDirective to satisfy the new interface requirement. However, I've noted an issue with the implementation in SiFormlyFormFieldProviderDirective where it doesn't fully adhere to the contract of SiFormItemControl regarding the assignment of aria-describedby, which is crucial for accessibility. Please see my detailed comment.
projects/element-ng/formly/wrapper/si-formly-form-field-provider.directive.ts
Show resolved
Hide resolved
|
Documentation. Coverage Reports: |
f9e81dc to
0d00bca
Compare
0d00bca to
fbe5d89
Compare
fbe5d89 to
5a1b28a
Compare
5a1b28a to
46a97f5
Compare
spike-rabbit
left a comment
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.
Seems like many of our examples are broken. Please fix them ideally in another PR upfront so we don't mix the changes here.
projects/element-ng/form/si-form-item/si-form-field-native.control.ts
Outdated
Show resolved
Hide resolved
projects/element-ng/ag-grid/components/ag-date-input.component.ts
Outdated
Show resolved
Hide resolved
74dee51 to
c1876c5
Compare
BREAKING CHANGE: The property `SiFormItemControl.errormessageId` is now required. All implementations of `SiFormItemControl` must provide this property to ensure proper accessibility support for error messages.
BREAKING CHANGE: The input `SiFormItemComponent.label` is now required.
c1876c5 to
2d4266b
Compare
BREAKING CHANGE: The property
SiFormItemControl.errormessageIdis now required. All implementations ofSiFormItemControlmust provide this property to ensure proper accessibility support for error messages.