-
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
refactor(animations): improve unit tests for stagger timing #47221
refactor(animations): improve unit tests for stagger timing #47221
Conversation
const animationDuration = 700; | ||
const absoluteStaggerDelay = 500; | ||
|
||
@Component({ |
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.
this gets wrongly indented by the formatter 馃槗
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.
ok I managed to fix it by shortening the it
text 馃檪
improve the stagger timing unit tests added in angular#47208 by also checking that the duration and keyframes of the players are correct
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 馃崻
Thanks, @dario-piotrowicz!
8f8b2d6
to
ae40aee
Compare
@jessicajaniuk I'm closing the PR as I will have to create a new one to fix the stagger issue you've found, so I guess it just makes more sense for me to include the updated unit tests in my next PR 馃檪 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
improve the stagger timing unit tests added in #47208 by also checking
that the duration and keyframes of the players are correct
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: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information