Fix Some Date and Time parsing cases #62376
Merged
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.
Fixes #61708
This change fixes two issues with the parser:
U+200F. This mark mainly helps when displaying the formatted date and time but it doesn't have any effect on the values or the separators. Our DateTime parser was not recognizing such mark and fails with any date/time strings containing such mark. This fix is addressing that by skipping this mark during the parse operation.dz-BTstarted formatting time with space separators. Something like10 30 PM. The parser was failing with such case too and this change is fixing it.