-
-
Notifications
You must be signed in to change notification settings - Fork 324
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
Translating with Composition API outside of template tags, does not load the right locale #1916
Comments
Thank you for your reporting! Unfortunately, I am not familiar astro. |
Thank you for your feadback! More infoWhy do I need to provide a reproduction?Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making. What will happen?If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect. If How can I create a reproduction?We have a couple of templates for starting with a minimal reproduction: 👉 Reproduction mininal starter A public GitHub repository is also perfect. 👌 Please ensure that the reproduction is as minimal as possible. You might also find these other articles interesting and/or helpful: |
Reporting a bug?
I'm using Astro + Vue and vue-i18n.
When translating using composition api, inside the "script setup" block, seems that Vue fallbacks to english locale for some reason.
After 10ms on load page (basically onMounted or onCompleted) the translation function uses the right locale fetched from the url.
But, after those 10ms, only the t('a') call inside the template is reactive, while the const variable in the setup script does not update.
Any way I could find a work-around for this?
Expected behavior
I'd expect to find a way to make the object reactive to locale changes.
Reproduction
System Info
Screenshot
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: