kazuya kawaguchi

hmm 🤔 I would like to support BigInt for NumberFormat, but, vue-i18n uses classic props, which results in a type error. 😭 https://github.com/vuejs/core/issues/5652

Thank you for your contrivution! First we would to confirm, I don't know from this PR what is the issue. Could you first explanation on the details of the issue...

@GalacticHypernova Thank you for your explanation! >should this change VueMessageType or should this be added as an overload of t? Curious to hear your opinion on how to proceed with...

> I mean, this would require unit testing of type inference, rather than regular types. It partially relies directly on the typescript engine. Does vitest have something to deal with...

@GalacticHypernova Sorry my late reply > I realized the TranslationComposer has a Locales property. When changing it to Messages[Locales] the autocomplete works but TS errors saying Locales can't be used...

Unfortunately, vue-i18n expects the message retrieved by `tm` to be an array, and the use case expectation is to resolve it using `rt`. It also expects the messages retrieved in...

Thank you for your reporting! Could you give us your minimal reproduction with github or stackblize, please?

Thank you for your reproduction! Unfortunately, I could not reproduce this issue. I saw the `Enfant` with `$t('children', 1)` 😞 We would need more information that is included reproduction.

Thank you for four feedback! Sorry late my reply. `te` will checks for the presence of a message by key for resources that vue-i18n has internally. For complex resources that...

This is interesting! vue-i18n has message format. we can extend for new syntax, but vue-i18n will be extend to like `Intl.MessageFormat` syntax, or adopt it for future. https://github.com/tc39/proposal-intl-messageformat we need...