Aral Roca Gomez
Aral Roca Gomez
I modified the last example allowing plurals: ```js t('example', { count: 5 }); // example_other ``` exact matches: ```js t('example', { count: 99 }); // example_99 ``` and tagged template...
I'd really like to find an elegant way to do it without needing to create next-translate.d.ts, but relying on the JSONs of the namespaces that everyone puts in is not...
for now I did a little improvement in 2.5 to simplify the `next-translate.d.ts` file: - Release notes: https://github.com/aralroca/next-translate-plugin/releases/tag/2.5.0 - Docs: https://github.com/aralroca/next-translate/blob/2.5.0/docs/type-safety.md Example: ```ts import type { Paths, I18n, Translate }...
@sandrooco it should work in the latest next-translate version. The implementation supports these 2 scenarios: 1. namespaces in `useTranslation` 2. keys in `t`: goes no further. No matter what parameters...
@valerioleo probably depends on the TypeScript version. Feel free to PR these missing parts. About `TemplateStringsArray` the only thing is ignore these cases: ```js t`some.key` ``` because for now is...
@StLyn4 exposing the internal context fix this issue or we need more things to do on this issue? thanks
Ok thanks @StLyn4, I don't know it neither. I leave the issue open, if someone finds a proposal to fix this feel free to PR 😊
@luknl https://simplelocalize.io/next-translate/
This should work in 2.0.0-canary.1. I close the issue. Feel free to reopen / comment if is not solved
Typescript version is already in Next-translate 2.0 😊