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
Tests fail with i18n version 0.9.3 #1132
Labels
Comments
tagliala
added a commit
to tagliala/faker
that referenced
this issue
Jan 27, 2018
Starting from version 0.9.3, I18n doesn't store translations for locales not set as available. This change set locales as available before storing translations. Fix: faker-ruby#1132 Ref: ruby-i18n/i18n#391
tagliala
changed the title
Failure with i18n version 0.9.3
Tests fail with i18n version 0.9.3
Jan 27, 2018
tagliala
added a commit
to tagliala/faker
that referenced
this issue
May 20, 2018
Starting from version 0.9.3, I18n doesn't store translations for locales not set as available. This change set locales as available before storing translations. Fix: faker-ruby#1132 Ref: ruby-i18n/i18n#391
tagliala
added a commit
to tagliala/faker
that referenced
this issue
Jun 21, 2018
Starting from version 0.9.3, I18n doesn't store translations for locales not set as available. This change set locales as available before storing translations. Fix: faker-ruby#1132 Ref: ruby-i18n/i18n#391
stympy
pushed a commit
that referenced
this issue
Jun 21, 2018
Starting from version 0.9.3, I18n doesn't store translations for locales not set as available. This change set locales as available before storing translations. Fix: #1132 Ref: ruby-i18n/i18n#391
davidmorton0
pushed a commit
to davidmorton0/faker
that referenced
this issue
Jul 12, 2021
Starting from version 0.9.3, I18n doesn't store translations for locales not set as available. This change set locales as available before storing translations. Fix: faker-ruby#1132 Ref: ruby-i18n/i18n#391
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to replicate:
Using i18n 0.9.3 (was 0.9.1)
)The reason should be ruby-i18n/i18n#391
I'm trying to submit a PR
The text was updated successfully, but these errors were encountered: