Use Date.now() and Date.parse() when a millisecond value is needed #6518
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use Date.now() and Date.parse() when a millisecond value is needed
Pull Request Type
Description
At the moment when we need to parse a date but get the millisecond value from it we call the
Date()
constructor and then call.getTime()
on it, in this pull request we instead useDate.parse()
which uses the same string date parsing algorithm as theDate()
constructor but directly produces a number of milliseconds. I also fixed another instance of using theDate()
constructor without any arguments and then calling.getTime()
on it, which wasn't caught by the linter (presumably because it was split up and.getTime()
was called multiple times).Testing
Desktop