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

feat(i18n): try to resolve $t from vue global properties #4244

Closed
m0ksem opened this issue Apr 29, 2024 · 0 comments · Fixed by #4256
Closed

feat(i18n): try to resolve $t from vue global properties #4244

m0ksem opened this issue Apr 29, 2024 · 0 comments · Fixed by #4256
Assignees

Comments

@m0ksem
Copy link
Contributor

m0ksem commented Apr 29, 2024

Beside our custom config, let's try to resolve $t from getCurrentInstance() global properties.
If $t is preset, try to resolve key like vuestic:${key}.

Add this feature to docs. This is much easier way to work with i18n.

In case if $t is not found, use the same approach we use rn.

Fsss126 added a commit to Fsss126/vuestic-ui that referenced this issue May 6, 2024
Fsss126 added a commit to Fsss126/vuestic-ui that referenced this issue May 8, 2024
m0ksem added a commit that referenced this issue May 23, 2024
* Try to resolve $t from vue global properties #4244

* fix(docs/i18n): move back vuestic key in example

* docs(i18n): remove extra steps in vue-i18n

---------

Co-authored-by: Maksim Nedoshev <m0ksem1337@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants