Describe the reason for these changes and the problem that they solve
As reported in #222, date/time related items in the application aren't being resolved correctly. It turns out that there were multiple underlying causes that resulted in this situation:
Additional dayjs locales were not imported, so we only had built-in default en-language content available
It turns out that most of the localization support required is bundled into modern browsers as part of the ECMAScript Internationalization API (aka Intl).
We should probably migrate to use that functionality natively in the near-ish future to reduce dependencies. To ease the transition until then, luxon is a neat near-drop-in replacement for dayjs that builds upon Intl (so it takes us one step in the correct direction).
Briefly summarize the changes
Provide an export from the application's i18n module to retrieve the current/resolved user-agent locale
Migrate from dayjs to luxon
How have the changes been tested?
Local development testing
List any issues that this change relates to
Fixes #222.
Describe the reason for these changes and the problem that they solve
As reported in #222, date/time related items in the application aren't being resolved correctly. It turns out that there were multiple underlying causes that resulted in this situation:
i18next.languagevalue used to determine the locale was not populated at runtimedayjslocales were not imported, so we only had built-in defaulten-language content availableIt turns out that most of the localization support required is bundled into modern browsers as part of the
ECMAScript Internationalization API(akaIntl).We should probably migrate to use that functionality natively in the near-ish future to reduce dependencies. To ease the transition until then,
luxonis a neat near-drop-in replacement fordayjsthat builds uponIntl(so it takes us one step in the correct direction).Briefly summarize the changes
i18nmodule to retrieve the current/resolved user-agent localedayjstoluxonHow have the changes been tested?
List any issues that this change relates to Fixes #222.