Context
Currently it is not possible to provide a date localizer when creating a new Date/Time picker, with it defaulting instead to an en-GB only version, or using moment.js if present. In 2.1.0 an Intl.DateTimeFormat variation was created.
Now that preferences can use the proper RFC5456 locales and IANA timezones, pcikers should be updated to allow custom date time localizers to be created and passed in as an option as opposed to doing a default lookup based on preferences.
The DefaultDateTimeLocalizer, IntlDateTimeLocalizer and MomentDateTimeLocalizer should be exposed, along with a way (either class or documentation) to allow custom ones to be created using other libraries.
Your Environment
Context
Currently it is not possible to provide a date localizer when creating a new Date/Time picker, with it defaulting instead to an
en-GBonly version, or usingmoment.jsif present. In 2.1.0 anIntl.DateTimeFormatvariation was created.Now that
preferencescan use the properRFC5456locales andIANAtimezones, pcikers should be updated to allow custom date time localizers to be created and passed in as an option as opposed to doing a default lookup based on preferences.The
DefaultDateTimeLocalizer,IntlDateTimeLocalizerandMomentDateTimeLocalizershould be exposed, along with a way (eitherclassor documentation) to allow custom ones to be created using other libraries.Your Environment