Improve user-friendly time parsing#226
Merged
atimin merged 1 commit intoJul 16, 2026
Merged
Conversation
yaslam-dev
marked this pull request as draft
May 31, 2026 10:38
Member
|
Hi @yaslam-dev , sorry for the late reply. You marked your PR as a draft, so I thought it wasn't ready and then forgot about it. It looks ready for review. Would you like to continue? Thank you for your contribution! |
atimin
changed the base branch from
main
to
yaslam-dev-feature/user-friendly-time-parsing
July 16, 2026 15:24
atimin
marked this pull request as ready for review
July 16, 2026 15:25
atimin
merged commit Jul 16, 2026
efa2781
into
reductstore:yaslam-dev-feature/user-friendly-time-parsing
1 check passed
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.
Closes #225
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
(Bug fix, feature, docs update, ...)
What was changed?
(Describe the changes)
Related issues
(Add links to related issues)
Does this PR introduce a breaking change?
(What changes might users need to make in their application due to this PR?)
Other information: