fix parseISO not returning Invalid Date when there are space(s) in passed string #1791
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 #1748. This PR adds additional validation when a datetime string is split using the existing RegEx in
splitDateString
, henceparseISO
will return "Invalid Date" for strings with space(s).Current
This PR
With that, the solution of this PR is to always check the resulting array length from
splitDateString
. If the array length is more than 2, then it contains space(s) and it should resolve to "Invalid Date".This is also considering the fact that ISO8601-formatted dates don't have spaces in it (source: https://www.w3.org/TR/NOTE-datetime).
Signed-off-by: Try Ajitiono [email protected]