-
-
Notifications
You must be signed in to change notification settings - Fork 500
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
Cannot access localePath in middleware #24
Comments
@RomainLK did you ever find a resolution to this? facing a similar issue using middleware to redirect based on a token existing within the store |
Still haven't found any resolution to this, :( |
Nevermind, actually found the answer to this looking at #25. https://github.com/nuxt-community/nuxt-i18n/pull/25/files#diff-6aeb88ffa6a6d00ecc6e8f0487e8d069R66 You can access localePath via |
Could this be corrected in the doc ? See: https://nuxt-community.github.io/nuxt-i18n/basic-usage.html#nuxt-link |
@mrleblanc101 done! Feel free to open PRs to help improve the doc, it can be done right in GitHub by clicking the |
* refactor: merge tests * refactor: merge tests (#24)
* refactor: merge tests * refactor: merge tests (nuxt-modules#24)
I'm making a middleware which redirects users to some pages depending on the store informations. However, I'm lacking
localePath
to localise the path for the redirect. I expected it to be available ascontext.app.localePath
, but it's not.More interestingly, it's available at
context.app.i18n.vm.localePath
but thethis
context is not correct.localePath
is somehow bound to a component which has neither$router
or$i18n
resulting in an error in i18n.routing.plugin.jsFor now I'm running out of idea. I suspect that it might be a problem with nuxt lifecycle between plugins / middleware but it's still obscure.
Versions:
nuxt: 1.3
nuxt-i18n: 2.2.4
The text was updated successfully, but these errors were encountered: