[WIP] defaults take precedence over fallbacks causing a misleading situation #413
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before proceeding with fixing the issues (even if I would need help with that) I opened a pull request with a failing test to explain it better.
The failing test is on line 28 (master...coorasse:add_fallback_issue_example#diff-514ab2ee25f5643b31473b6383cf04e7R28) and, as you can see, it shouldn't fail, since the test on the previous line works fine.
In other words: if I have a string translated, I don't expect it not to be translated because I add a default value.
That unfortunately happened in our Rails app and took me some time to dig into the issue.
Funny fact: when using a Chain backend
I18n.backend = I18n::Backend::Chain.new(Backend.new, I18n::Backend::Simple.new)
the same does not happen since thedefault
options are passed only to the last backend of the chain.