Repository navigation
Feature request: support TR35 (Unicode LDML) date format patterns, or provide a TR35 → Quasar converter #18592
Unanswered
NHenzen
asked this question in
Ideas / Proposals
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
Quasar uses its own date format tokens (e.g.
DD-MM-YYYY,YYYY/MM/DD), which differ from the Unicode standard (UTS #35 / TR35) used by most of the JS ecosystem and other platforms. Libraries such asdate-fnsandIntl/ICU-based tooling use TR35 patterns, e.g.dd-MM-yyyyoryyyy/MM/dd.This creates friction in projects that combine Quasar with other date tools:
Example
YYYY-MM-DDyyyy-MM-ddDD-MM-YYYYdd-MM-yyyyYYYY/MM/DDyyyy/MM/ddWhere this affects Quasar
Date-utils formar)QDatemaskpropWhat I would like to see
Support for the TR35 (Unicode LDML) date format standard in Quasar, either:
yyyy/MM/dd) in Quasa, ideally as an opt-in so existing Quasar formats keep working and nothing breaks.References
All reactions