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): not throwing error for unknown properties on container nodes #29691

Closed
wants to merge 1 commit into from

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Apr 3, 2019

Fixes Ivy not throwing an error if it runs into an invalid property binding on a container node (e.g. <div *ngFor="let row of rows"> instead of <div *ngFor="let row if rows">).

This PR resolves FW-1219.

@crisbeto crisbeto added comp: ivy action: review The PR is still awaiting reviews from at least one requested reviewer type: bug/fix labels Apr 3, 2019
@ngbot ngbot bot added this to the needsTriage milestone Apr 3, 2019
@crisbeto crisbeto marked this pull request as ready for review April 3, 2019 21:03
@crisbeto crisbeto requested a review from a team as a code owner April 3, 2019 21:03
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.

LGTM, just 1 nit

packages/core/test/linker/integration_spec.ts Outdated Show resolved Hide resolved
@kara kara added action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Apr 8, 2019
Fixes Ivy not throwing an error if it runs into an invalid property binding on a container node (e.g. `<div *ngFor="let row of rows">` instead of `<div *ngFor="let row if rows">`).

This PR resolves FW-1219.
@crisbeto crisbeto removed their assignment Apr 8, 2019
@crisbeto crisbeto added action: review The PR is still awaiting reviews from at least one requested reviewer and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Apr 8, 2019
@crisbeto
Copy link
Member Author

crisbeto commented Apr 8, 2019

I've reworked it based on the feedback @kara.

@kara kara added action: merge The PR is ready for merge by the caretaker action: presubmit The PR is in need of a google3 presubmit and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Apr 8, 2019
@kara
Copy link
Contributor

kara commented Apr 8, 2019

presubmit

@kara kara added target: major This PR is targeted for the next major release and removed action: presubmit The PR is in need of a google3 presubmit labels Apr 8, 2019
@IgorMinar IgorMinar closed this in d144a3b Apr 8, 2019
DeveloperFromUkraine pushed a commit to DeveloperFromUkraine/angular that referenced this pull request Apr 11, 2019
angular#29691)

Fixes Ivy not throwing an error if it runs into an invalid property binding on a container node (e.g. `<div *ngFor="let row of rows">` instead of `<div *ngFor="let row if rows">`).

This PR resolves FW-1219.

PR Close angular#29691
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
angular#29691)

Fixes Ivy not throwing an error if it runs into an invalid property binding on a container node (e.g. `<div *ngFor="let row of rows">` instead of `<div *ngFor="let row if rows">`).

This PR resolves FW-1219.

PR Close angular#29691
@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 14, 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 target: major This PR is targeted for the next major release type: bug/fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants