fix(util/number): the parseDate function failed to parse a date string like 2020-07-29 09:2:5.
#13044
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
…g like `2020-07-29 09:2:5`.
|
Thanks for your contribution! The pull request is marked to be |
100pah
approved these changes
Jul 29, 2020
|
Congratulations! Your PR has been merged. Thanks for your contribution! |
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.
Brief Information
This pull request is in the type of:
What does this PR do?
Fix a bug that the
parseDatefunction can not parse a date string like2020-07-29 09:2:5.The minute/second has only one number, not padding with 0.
Others
Merging options
Other information
Another potential bug about time is mentioned in #13039 (comment)