Skip to content

Conversation

tbosch
Copy link
Contributor

@tbosch tbosch commented Mar 23, 2017

This has the side effect of allowing @Input and @ContentChild
on the same property if the query is static (see the bug description
for details).

Fixes #15417

Please check if the PR fulfills these requirements

What kind of change does this PR introduce? (check one with "x")

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)

What is the new behavior?

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

This has the side effect of allowing `@Input` and `@ContentChild`
on the same property if the query is static (see the bug description
for details).

Fixes angular#15417
@tbosch tbosch added the action: merge The PR is ready for merge by the caretaker label Mar 23, 2017
@vicb vicb merged commit c8ab5cb into angular:master Mar 23, 2017
@tbosch tbosch deleted the fix_reg1 branch April 28, 2017 23:40
asnowwolf pushed a commit to asnowwolf/angular that referenced this pull request Aug 11, 2017
This has the side effect of allowing `@Input` and `@ContentChild`
on the same property if the query is static (see the bug description
for details).

Fixes angular#15417
juleskremer pushed a commit to juleskremer/angular that referenced this pull request Aug 28, 2017
This has the side effect of allowing `@Input` and `@ContentChild`
on the same property if the query is static (see the bug description
for details).

Fixes angular#15417
@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 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4.0.0-rc.6 regression: using @Input() @ContentChild() on the same property breaks input
5 participants