Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

marclaval
Copy link
Contributor

Found this issue while adding more directives' hooks tests

@marclaval marclaval added action: review The PR is still awaiting reviews from at least one requested reviewer target: major This PR is targeted for the next major release comp: ivy labels Feb 21, 2018
@marclaval marclaval requested a review from kara February 21, 2018 17:22
@trotyl
Copy link
Contributor

trotyl commented Feb 21, 2018

Violating #10221 (comment) ?

Copy link
Contributor

@kara kara left a 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', () => {
Copy link
Contributor

@kara kara Feb 21, 2018

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', () => {
Copy link
Contributor

@kara kara Feb 21, 2018

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.

@kara
Copy link
Contributor

kara commented Feb 21, 2018

Discussed with @Mlaval offline, closing

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: review The PR is still awaiting reviews from at least one requested reviewer cla: yes target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants