Fix US locale datetime parsing#2262
Merged
texodus merged 1 commit intoperspective-dev:masterfrom Jun 24, 2023
Merged
Conversation
Contributor
Author
|
@texodus / @sc1f / @timkpaine could you please review my PR on issue #1312 |
texodus
approved these changes
Jun 24, 2023
Member
texodus
left a comment
texodus
left a comment
There was a problem hiding this comment.
Thanks for the PR! Looks good!
texodus
changed the title
texodus
changed the title
datetime parsing
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.
Fix for isssue( #1312 ) where US locale string format ("%m/%d/%Y, %I:%M:%S %p") is parsed wrongly by emscripten compiler. eg. "03/15/2020, 11:30:45 AM" is incorrectly parsed as "03/15/2020, 11:30:45 PM"
Before Implementation - Test Fails
After Implementations - Test Passes
