-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
fix(ivy): Content and View hooks are component-only #22351
Conversation
Violating #10221 (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.
This PR would change the behavior so that it doesn't match current Angular behavior. Since we should be backwards compatible, I'm not sure what the motivation for the PR is?
expect(events).toEqual(['comp']); | ||
}); | ||
|
||
it('should not be called on directives on an element', () => { |
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.
This does not match current Angular behavior. Directives on an element or a component will still call content hooks.
expect(events).toEqual(['comp']); | ||
}); | ||
|
||
it('should not be called on directives on an element', () => { |
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.
This does not match current Angular behavior. Directives on elements and components both call view hooks.
Discussed with @Mlaval offline, closing |
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. |
Found this issue while adding more directives' hooks tests