-
Notifications
You must be signed in to change notification settings - Fork 6.8k
docs: expand example that removes value accessor provider #13860
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
docs: expand example that removes value accessor provider #13860
Conversation
{ | ||
provide: NG_VALUE_ACCESSOR, | ||
useExisting: forwardRef(() => MatFormFieldControl), | ||
multi: true, |
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.
Is the indentation intentional here?
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.
Looks like I took this from somewhere that was indented with tabs, instead of spaces.
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.
Should we show the provider commented out or something? To make it easier to notice that they're supposed to remove this
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.
Done.
In the form field guide, we instruct people to remove the `NG_VALUE_ACCESSOR` provider and replace it with injecting the `NgControl`, however it's not very explicit and is easy to miss. These changes expand the example a bit in an effort to make it harder to miss. Fixes angular#8158.
c1bd5d5
to
f6b179e
Compare
In the form field guide, we instruct people to remove the `NG_VALUE_ACCESSOR` provider and replace it with injecting the `NgControl`, however it's not very explicit and is easy to miss. These changes expand the example a bit in an effort to make it harder to miss. Fixes #8158.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
In the form field guide, we instruct people to remove the
NG_VALUE_ACCESSOR
provider and replace it with injecting theNgControl
, however it's not very explicit and is easy to miss. These changes expand the example a bit in an effort to make it harder to miss.Fixes #8158.