-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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: add documentation for ngNonBindable #36560
Conversation
This needs engineering review and finalizations |
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.
Looking good! I have offered a few minor suggestions
6ed34ae
to
5030000
Compare
@aikidave made the changes please have a look |
and will not display `2`. This is helpful when you want to render code in the browser. | ||
|
||
When you apply `ngNonBindable` to an element, it stops any binding starting at that element, including child elements. However, `ngNonBindable` still allows | ||
directives to work to the element where you apply`ngNonBindable`. In the following example, the `appHighlight` directive will still be active but Angular will not evaluate the expression `{{ 1 +1 }}`. |
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.
Excuse me, If I could give my two cents here, I think there are missing whitespaces:
- After "apply" word;
- After plus sign (there are other ocurrences also in file "app.component.html");
directives to work to the element where you apply`ngNonBindable`. In the following example, the `appHighlight` directive will still be active but Angular will not evaluate the expression `{{ 1 +1 }}`. | |
directives to work to the element where you apply `ngNonBindable`. In the following example, the `appHighlight` directive will still be active but Angular will not evaluate the expression `{{ 1 + 1 }}`. |
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.
Thanks will add them in the changes
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.
Good catch, @rafaelss95!
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.
made the changes @aikidave please have a look
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.
@ajitsinghkaler it seems like you forgot to change it in the app.component.html
also 👀
@mhevery can ou please have a look |
@mhevery can you please have a look |
f0cc085
to
9fd0463
Compare
@mhevery can you please review this @aikidave can you please put a tag that it needs eng input |
9fd0463
to
077c075
Compare
ngNonBindable documentation was not present, on docs site added documentation for ngNonBindable. With this template primitive, Angular won't evaluate expressions in elements. Fixes angular#28577 Fixes angular#19497
077c075
to
589859d
Compare
@mhevery can you please review this |
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. |
Ng non-bindable documentation was not present added documentation for ng non-bindable
@kapunahelewong was adding this documentation in #28577 asked me to take over for her as she doesn't have time to complete
Fixes #28577 #19497
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
no ngNonBindable documentation
Issue Number: #19497
What is the new behavior?
added ngNonBindable documentation
Does this PR introduce a breaking change?
Other information