You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I was not sure if it's a feature request or a bug report, but here it is:
On our project we using react-native-localize together with date-fns-tz. And we have faced the problem during last review by apple.
I have opened issue for date-fns-tz repo previously and here's their response: marnusw/date-fns-tz#241
After this long intro my question is: is it possible to add support for getTimeZone function to return the time zone in a given format (INAA, for example). In order to prevent unexpected crashed and improve UX of date formatting.
Possible implementation
Provide optional value of format to getTimeZone function. And add mapping of aliases to zone ID according to https://nodatime.org/timezones
Code sample
No response
The text was updated successfully, but these errors were encountered:
Time zone database entries such as “America/Los_Angeles” are IDs, not names. An example of a time zone name is “Pacific Daylight Time”. Although many NSTimeZone symbols include the word “name”, they actually refer to IDs.
I also found this article with some kind of solution.
Why it is needed?
Hi!
I was not sure if it's a feature request or a bug report, but here it is:
On our project we using
react-native-localize
together withdate-fns-tz
. And we have faced the problem during last review by apple.I have opened issue for
date-fns-tz
repo previously and here's their response: marnusw/date-fns-tz#241After this long intro my question is: is it possible to add support for
getTimeZone
function to return the time zone in a given format (INAA, for example). In order to prevent unexpected crashed and improve UX of date formatting.Possible implementation
Provide optional value of
format
togetTimeZone
function. And add mapping ofaliases
tozone ID
according to https://nodatime.org/timezonesCode sample
No response
The text was updated successfully, but these errors were encountered: