-
Notifications
You must be signed in to change notification settings - Fork 27k
docs(lifecycle-hooks): updates directive event hooks real capabilities #16654
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
Conversation
8427868 to
28981df
Compare
aio/content/guide/lifecycle-hooks.md
Outdated
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.
Respond the first time Angular has checked the content children of a directive/component.
aio/content/guide/lifecycle-hooks.md
Outdated
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.
Respond every time Angular has checked the content children of a directive/component.
aio/content/guide/lifecycle-hooks.md
Outdated
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.
Respond the first time Angular has checked the component's view / the view that a directive is in.
aio/content/guide/lifecycle-hooks.md
Outdated
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.
Respond every time Angular has checked the component's view / the view that a directive is in.
b1a8775 to
682877f
Compare
|
@tbosch PR updated 😄 |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
afb0b92 to
682877f
Compare
|
CLAs look good, thanks! |
|
any plan to merge this? |
|
Hm...not sure what happened here. Looks like it should have been merged a while ago. |
|
Sure!
…On Fri, Nov 10, 2017 at 4:11 AM George Kalpakas ***@***.***> wrote:
Hm...not sure what happened here. Looks like it should have been merged a
while ago.
@Drumarcco <https://github.com/drumarcco>, can you please rebase on
latest master?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16654 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIuU0PRGK0Po_hkzsfQKt4Qw_EDXu5c6ks5s1C95gaJpZM4NVmcI>
.
|
Minor documentation update to include event hooks that were assumed to only work on components. Closes angular#10221
682877f to
8c72579
Compare
|
PR Updated, CI failed for some reason 🤔 |
|
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. |
Minor documentation update to include event hooks that were assumed to only work on components.
Closes #10221
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
The docs assume some event hooks don't work on directives when they actually do.
What is the new behavior?
The docs are updated to match directives' real capabilities.
Does this PR introduce a breaking change? (check one with "x")
Other information:
It's the same as this PR angular/angular.io#2816 but applied on angular/angular