Added support for microsecond precision for timestamps #603
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.
Added support for microsecond precision for timestamps in time period duration calculations and timestamp progress indicators.
Example timestamp: 2023-09-26 18:24:17.035169
Before this change, only millisecond precision was supported, so the last three digits in the timestamp above was lost. This was caused by limited time precision support in Javascript and the new microsecond precision has required explicit handling in the extension to keep track of the number of microseconds.
Also did some refactoring and rewriting of unit tests.
Fixes #65 and #594.