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
Namespace lookup does not include fallback keys #368
Comments
This might be complex on computation, as it requires run logic on each key located inside the namespace. Are you using |
I'm not doing anything special, so I guess I'm using the For my special use case of needing to extract all translations from a specific namespace including the fallbacks, I worked around the current behavior by doing a second namespace lookup in the default locale and performing a deep merge. From my point of view, it would be more consistent if that was the default behavior, but I'm not sure I understand all the implications and also there might be a performance trade off. |
Hi, this issue might be fixed by #387. Could you please try it out and let me know? |
@radar Tried 0.9.0 and saw unchanged behavior far as I can tell. |
hi, |
If there was, you can be sure it would be posted here. |
What I tried to do
Given locales like:
What I expected to happen
Looking up a single translation falls back to default locale:
Looking up a namespace should return the same results as an object:
What actually happened
Since the namespace key is found, fallback logic does not kick in:
Versions of i18n, rails, and anything else you think is neccessary
I18n 0.8.1
Rails 4.2
The text was updated successfully, but these errors were encountered: