Open noahtallen opened 10 months ago
I have the same problem, but I noticed that it depends on the folder name, for example, if folder name is articles/manufacturer - I always secondary locale or empty string, if I rename folder to blogs/partner - problem solved.
Project structure, also maybe it's because the manufacturer/articles folder on top
Describe the bug Sometimes (leaving the question of whether this is a good idea to the side for now ;)), you may do an internal API request as part of rendering a page. In this scenario, astro-i18n shows the default locale, and translations do not work.
Node will issue an API request, which will ultimately come back to Astro, which the i18n middleware will handle, before the original request is finished.
I am curious what the core issue is here -- shouldn't the request to
/api/data
be isolated, meaning that the original request to http://localhost:4321/es still gets the correct locale?To Reproduce
npm i && npm run dev
c63fd1b
to see the translations working.Expected behavior Locale & translations should still work
Mandatory reproduction repository https://github.com/noahtallen/astro-i18n-minimal-bug-report