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
One of the k6's users reported that using the Date().toLocaleDateString() always returns the date in the same format.
Date().toLocaleDateString()
Date().toLocaleDateString('en-US') Expect 12/30/2012 : Actual 12/30/2012 Date().toLocaleDateString('en-CA') Expect 2012-12-30 : Actual 12/30/2012 Date().toLocaleDateString('en-GB') Expect 30/12/2012 : Actual 12/30/2012 Date().toLocaleDateString('de-DE') Expect 30.12.2012 : Actual 12/30/2012
It's happening since internally, the only dateLayout_en_GB is used, and we don't take into account any arguments.
dateLayout_en_GB
Probably, that's not what most users will expect.
Fixing this will help satisfy users' expectations.
The text was updated successfully, but these errors were encountered:
I don't see how it's possible without involving a 3rd party library, any suggestions?
Sorry, something went wrong.
No branches or pull requests
What?
One of the k6's users reported that using the
Date().toLocaleDateString()
always returns the date in the same format.It's happening since internally, the only
dateLayout_en_GB
is used, and we don't take into account any arguments.Probably, that's not what most users will expect.
Why?
Fixing this will help satisfy users' expectations.
The text was updated successfully, but these errors were encountered: