Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typed in the composable useI18n('key') and in $t('key') #1817

Closed
2 of 4 tasks
sawa-ko opened this issue Jan 24, 2023 · 2 comments
Closed
2 of 4 tasks

Typed in the composable useI18n('key') and in $t('key') #1817

sawa-ko opened this issue Jan 24, 2023 · 2 comments

Comments

@sawa-ko
Copy link

sawa-ko commented Jan 24, 2023

Describe the feature

It would be great if when setting a translation key it would come with typescript typing based on the default language json file structure, this way you can avoid accidental typing errors in translation keys and provide the developer with a better environment as he can see what translation keys he has available in a list without the need for external tools.

I have seen this idea in next-intl and it looks very interesting.
https://next-intl-docs.vercel.app/docs/usage/typescript

Additional information

  • Would you be willing to help implement this feature?
  • Could this feature be implemented as a module?

Final checks

@sawa-ko sawa-ko changed the title Typed in the composable useI18n() and in $t() Typed in the composable useI18n('key') and in $t('key') Jan 24, 2023
@ineshbose
Copy link
Collaborator

#1753

Copy link
Collaborator

kazupon commented Jan 29, 2023

Hi!
Thank you for your feedback!
The same issue is already in #1753.

So, close

@kazupon kazupon closed this as not planned Won't fix, can't repro, duplicate, stale Jan 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants