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

test(select): flush pending microtasks from other components #1396

Merged
merged 2 commits into from
Apr 18, 2019
Merged

test(select): flush pending microtasks from other components #1396

merged 2 commits into from
Apr 18, 2019

Conversation

yggg
Copy link
Contributor

@yggg yggg commented Apr 18, 2019

There is two task pending. One from button setTimeout and another from
spinner service.

Please read and mark the following check list before creating a pull request:

Short description of what this resolves:

There is two task pending. One from button setTimeout and another from
spinner service (I have no idea why spinner micro task showed up. It's code here since 2017).

There is two task pending. One from button setTimeout and another from
spinner service.
@yggg yggg requested a review from nnixaa April 18, 2019 15:40
…crotasks-it-was-not-an-issue-for-some-reason-but-now-it-is-yes-i-added-set-timeout-in-button-but-spinner-service-load-all-last-changed-in-2017-whyyyyyy
@yggg yggg merged commit 064b2cf into akveo:next Apr 18, 2019
@yggg yggg deleted the fix/select-tests-flush-button-and-spinner-microtasks-it-was-not-an-issue-for-some-reason-but-now-it-is-yes-i-added-set-timeout-in-button-but-spinner-service-load-all-last-changed-in-2017-whyyyyyy branch April 18, 2019 16:00
@yggg yggg restored the fix/select-tests-flush-button-and-spinner-microtasks-it-was-not-an-issue-for-some-reason-but-now-it-is-yes-i-added-set-timeout-in-button-but-spinner-service-load-all-last-changed-in-2017-whyyyyyy branch April 18, 2019 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants