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
The current locale formats roughly correspond to the short and medium formats in CLDR. I suggest adding the long and full formats as well. Given that banglejs is first and foremost a watch, it makes sense to me that there is extensive support for datetime formats. I can also see that some of the locales use longer formats in the long version. I have mentioned in #3268 that we probably need to make those shorter to ensure compat with apps, but we could still allow apps to explicitly opt in to a longer format by supporting all four CLDR formats.
Because the data is autogenerated from CLDR data, this change can be applied by me for all locales.
The text was updated successfully, but these errors were encountered:
In #3268 I suggest using the CLDR data to autogenerate locale information. But the current locale data only provides a
short
andlong
option. The CLDR data supports four lengths:short
,medium
,long
andfull
. You can see an example here: https://www.npmjs.com/package/cldr#cldrextractdateformatslocaleidroot-calendaridgregorianThe current
locale
formats roughly correspond to theshort
andmedium
formats in CLDR. I suggest adding thelong
andfull
formats as well. Given that banglejs is first and foremost a watch, it makes sense to me that there is extensive support for datetime formats. I can also see that some of the locales use longer formats in thelong
version. I have mentioned in #3268 that we probably need to make those shorter to ensure compat with apps, but we could still allow apps to explicitly opt in to a longer format by supporting all four CLDR formats.Because the data is autogenerated from CLDR data, this change can be applied by me for all locales.
The text was updated successfully, but these errors were encountered: