-
-
Notifications
You must be signed in to change notification settings - Fork 8
set options timeZoneName is not working #25
New issue
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
Comments
@lruiz-empyrean Does this return correct datetime for any given timezone? |
The current version doesn't, but changing the timezone before formatting it would, as long as you use the time zone IDs, such as: "UTC", "America/Argentina/Buenos_Aires", "America/Aruba", "America/Chicago", etc. Reference: Example: // 'UTC' // 'America/Argentina/Buenos_Aires' // 'America/Aruba' // 'America/Chicago' |
I see. Could you provide your native example please?
EDITED: It seems device does not support 'UTC' :D |
In the end, I've just inherited from the DatetimeFormat and overrode the current formatNative function in the library
and then I used the new class the same as the original.
That's a good point to take into account. |
Hello,
I'm trying to use the options to set the timeZoneName so the string comes formatted using that time zone
I have something like this
the result should be Jan 1, 2020, but the timeZoneName is being ignored, I'm receiving Dec 31, 2019, instead
Looking at the code, I think I found a solution for that, it could be done in the formatNative function
something like this
Creating the corresponding
getNativeTimeZone
methodsIf you'd like I can make the pull request
The text was updated successfully, but these errors were encountered: