For better code organization, perennity, and simpler maintenance, we should fully switch frontend translations management to inlang's newly released paraglide-js. It solves ICU message formatting, message extraction/generation from json sources, and more.
This is somewhat a low hanging fruit as a full setup has been tested and confirmed in a skeleton project.
List of actions
[ ] In terms of semantics, use lang rather than locale for clarity (even if not necessarily as concise)
[x] Deprecate in-house locale constants and helpers where paraglide offers generated alternatives
[ ] Replace all uses of createTranslations with message functions
[x] Co-locate ALL messages in respective messages/(lang).json source files.
[ ] Improve code clarity and organization for handle hook, layout data, and etc.
Task Description
For better code organization, perennity, and simpler maintenance, we should fully switch frontend translations management to inlang's newly released paraglide-js. It solves ICU message formatting, message extraction/generation from json sources, and more.
This is somewhat a low hanging fruit as a full setup has been tested and confirmed in a skeleton project.
List of actions
langrather thanlocalefor clarity (even if not necessarily as concise)createTranslationswith message functionsmessages/(lang).jsonsource files.