More robust date parsing#3068
Merged
Merged
Conversation
Luna712
approved these changes
Jul 14, 2026
Luna712
left a comment
Luna712
left a comment
Contributor
There was a problem hiding this comment.
Thank you! Sorry I missed this one...
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.
The date parsing fails at "2026-05-17 12:30:45" when the previous implementation managed to parse it. This was the best solution but it still loses the "12:30:45" part, which is fair considering the format is "yyyy-MM-dd".