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

Can't handle setting "now" to 0, returns Date.now() instead #169

Open
noyesa opened this issue Nov 29, 2021 · 0 comments
Open

Can't handle setting "now" to 0, returns Date.now() instead #169

noyesa opened this issue Nov 29, 2021 · 0 comments

Comments

@noyesa
Copy link

noyesa commented Nov 29, 2021

This line considers a value of 0 to be falsy, so if you use this it will continue to return the value of Date.now() if you use dateService.setNow(0). This was unexpected to me since it continued to use the real time in my test.

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

No branches or pull requests

1 participant