Skip to content

fix(ivy): ensure that super/sub classes can both update an animation binding in harmony#29978

Closed
matsko wants to merge 1 commit intoangular:masterfrom
matsko:FW-1220-fix_animation_transition_states_ivy
Closed

fix(ivy): ensure that super/sub classes can both update an animation binding in harmony#29978
matsko wants to merge 1 commit intoangular:masterfrom
matsko:FW-1220-fix_animation_transition_states_ivy

Conversation

@matsko
Copy link
Contributor

@matsko matsko commented Apr 18, 2019

In ivy, because metadata is inherited, this may cause super and sub host bindings on
two components to update an animation binding in parallel. This patch ensures that
the animation transition code can handle this.

Jira-Issue: FW-1220

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@matsko matsko force-pushed the FW-1220-fix_animation_transition_states_ivy branch from 195a4a1 to f997d07 Compare April 18, 2019 18:11
@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@matsko matsko force-pushed the FW-1220-fix_animation_transition_states_ivy branch from f997d07 to db4e609 Compare April 18, 2019 18:51
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't fromState always be truthy now? Is that intended?

@ngbot ngbot bot modified the milestone: needsTriage Apr 18, 2019
@gkalpak gkalpak mentioned this pull request Apr 19, 2019
16 tasks
@matsko matsko force-pushed the FW-1220-fix_animation_transition_states_ivy branch 2 times, most recently from 4444cc1 to 327532c Compare April 19, 2019 20:38
@matsko
Copy link
Contributor Author

matsko commented Apr 19, 2019

@mary-poppins
Copy link

You can preview 195a4a1 at https://pr29978-195a4a1.ngbuilds.io/.
You can preview f997d07 at https://pr29978-f997d07.ngbuilds.io/.
You can preview db4e609 at https://pr29978-db4e609.ngbuilds.io/.
You can preview 4444cc1 at https://pr29978-4444cc1.ngbuilds.io/.
You can preview 327532c at https://pr29978-327532c.ngbuilds.io/.

@matsko matsko closed this Apr 22, 2019
@matsko matsko force-pushed the FW-1220-fix_animation_transition_states_ivy branch from 327532c to 3f6bf6d Compare April 22, 2019 03:15
…binding in harmony

In ivy, because metadata is inherited, this may cause super and sub host bindings on
two components to update an animation binding in parallel. This patch ensures that
the animation transition code can handle this.

Jira-Issue: FW-1220
@matsko matsko reopened this Apr 22, 2019
@mary-poppins
Copy link

You can preview 3f6bf6d at https://pr29978-3f6bf6d.ngbuilds.io/.

@mary-poppins
Copy link

You can preview ab6b89a at https://pr29978-ab6b89a.ngbuilds.io/.

@gkalpak
Copy link
Member

gkalpak commented Apr 23, 2019

Is this superceded by #30022?

@matsko matsko closed this Apr 25, 2019
@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 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants