Remove string_to_utc_time conversion function
#272
Merged
Conversation
This file contains 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
This method was used in features that were removed (#268 and #271) and the reason for converting ts values selected from the timeline query is not explicitly documented in the commit history and appears to be redundant (they are already timestamps) After conducting manual tests on the `usec`s, it was determined that the issue reported in issue #32 is no longer valid.
tagliala
force-pushed
the
chore/remove-string-to-utc-conversion
branch
from
46a9d22
to
de6eb98
Compare
tagliala
added a commit
that referenced
this pull request
Jun 2, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This method was used in features that were removed (#268 and #271) and the reason for converting ts values selected from the timeline query is not explicitly documented in the commit history and appears to be redundant (they are already timestamps)
After conducting manual tests on the
usecs, it was determined thatthe issue reported in issue #32 is no longer valid.