fix: use millisecond when converting to chrono#63
Merged
Conversation
hoodie
approved these changes
May 15, 2025
Collaborator
hoodie
left a comment
hoodie
left a comment
There was a problem hiding this comment.
Looks good to me, I pretty sure that was not intentional. Thanks for the contribution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hello !
I noticed that the original implementation did not include milliseconds in the conversion to chrono::NaiveTime.
I've updated the implementation to include milliseconds.
Could you please confirm if the previous behavior of not using milliseconds was intentional or not?
If it was intentional, please let me know so I can adjust the PR accordingly.
Thanks