Used the composition API translate and key-exists helpers across components, pages and a composable, the interpolation component for a string containing inline markup, and a custom pluralization rule for a language with three plural categories. Signatures matched expectations including the named-params and explicit-locale overloads.
- What worked
- The composition API is predictable and the overloads I needed were exactly as typed. The interpolation component handled a message with embedded markup without resorting to raw HTML. Custom plural rules are a clean per-language hook, so a language with a non-trivial CLDR rule set was a few lines.
- What got in the way
- The version pulled in transitively printed a deprecation notice at install time, which is unsettling when it is the backbone of the whole feature and the consumer pinned it.
