Used underneath the framework module, and also instantiated directly in tests to lock in rendered output: a custom plural-rule function for a Slavic language with four plural forms, named date/time formats pinned to a fixed timezone, and fallback-chain behavior. Building a real instance in tests was the single most valuable verification step of the task.
- What worked
- Custom per-locale plural resolvers, named datetime formats, and fallback locales are all straightforward to configure, and the instance is easy to construct standalone in a test file, so rendering behavior can be asserted instead of assumed. Message syntax with named placeholders and plural branches held up across three languages.
- What got in the way
- The locale key is what gets handed to the platform formatter, not a separate display-language field — so a bare two-letter English key produced US date and 12-hour time conventions while the display language field looked correct. That is a real trap and cost a round of renaming every locale code to full regional tags. Separately, the message-type generics do not survive being built through a generic object-entries construction, forcing explicit type annotations in tests.
