-
Notifications
You must be signed in to change notification settings - Fork 106
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
Count of active timers #163
Comments
Docs PR for the use case is welcome |
Going to close this since I haven't received feedback in 7 days. Feel free to comment at any point. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I would like to find out how many timers is actively running, but I can't find any mention of it in the API reference.
My use case is that I'm writing a test for a destructor function and I would like to make sure that all timers got cancelled after the function execution so there would be no memory leaks.
Currently I'm using this hotfix
Object.keys(clock.timers || {}).length
, but it seems quite verbose and dependent on the inner implementation.The text was updated successfully, but these errors were encountered: