-
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(animations): fix stagger timing not handling params #47233
base: main
Are you sure you want to change the base?
fix(animations): fix stagger timing not handling params #47233
Conversation
prior to this change the stagger timing was being built during the ast building instead of dynamically when visiting the stagger animation, thus it could not handle params correctly, this change makes it so that during ast building a timing ast is built instead and that ast is used dynammically to build animations which can handle params correctly (this PR reinstates the changes done in angular#47208 which have been reverted because negative non-parametrized stagger values were not handled correctly, alongside the original changes the current commit also handles corretly negative non-parametrized values and improves unit testing) resolves angular#19786
3683177
to
230bdb8
Compare
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.
LGTM 馃崻
We'll want to run a TGP just to be safe.
yeah of course 馃槄馃憤 |
Hello! Greetings, Flo |
@jessicajaniuk @dario-piotrowicz Hello! Will this feature coming soon, or is it histroy? I see the pull requests fails? Thx and greetings, |
prior to this change the stagger timing was being built during the
ast building instead of dynamically when visiting the stagger animation,
thus it could not handle params correctly, this change makes it so that
during ast building a timing ast is built instead and that ast is used
dynammically to build animations which can handle params correctly
(this PR reinstates the changes done in #47208 which have been reverted
because negative non-parametrized stagger values were not handled
correctly, alongside the original changes the current commit also
handles corretly negative non-parametrized values and improves unit
testing)
resolves #19786
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #19786
Does this PR introduce a breaking change?
Other information