We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing a date with correct separator works and is correct:
> Globalize('en').parseDate('1/2/17', {skeleton: 'yMd'}) 0017-01-02T02:00:00.000Z
Parsing a date with incorrect separator currently works, but it's correct:
> Globalize('en').parseDate('1-2-17', {skeleton: 'yMd'}) 0017-01-02T02:00:00.000Z > Globalize('en').parseDate('1.2.17', {skeleton: 'yMd'}) 0017-01-02T02:00:00.000Z > Globalize('en').parseDate('1.2.2017', {skeleton: 'yMd'}) 2017-01-02T02:00:00.000Z > Globalize('en').parseDate('10.2.2017', {skeleton: 'yMd'}) 2017-10-02T03:00:00.000Z > Globalize('en').parseDate('10a2a2017', {skeleton: 'yMd'}) 2017-10-02T03:00:00.000Z
The text was updated successfully, but these errors were encountered:
Date: Parse literals, e.g., separators
3f99445
Fixes globalizejs#683
2568ce7
No branches or pull requests
Parsing a date with correct separator works and is correct:
Parsing a date with incorrect separator currently works, but it's correct:
The text was updated successfully, but these errors were encountered: