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

Added support for microsecond precision for timestamps #603

Merged
merged 5 commits into from
Jul 19, 2024

Conversation

emilast
Copy link
Owner

@emilast emilast commented Jul 18, 2024

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.

- Time duration calculation
- Time progress indicators
…lasses

The calculations are now more maintainable since they are contained properly.
It's a much better separation of concerns to let TimePeriod do it instead of TimePeriodController.
@emilast emilast merged commit aea583a into master Jul 19, 2024
2 checks passed
@emilast emilast deleted the feature/594-microseconds branch July 19, 2024 20:58
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.

Microsecond (custom) precision in selected logs duration
1 participant