Properly translate renamed resources #2044
Merged
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.
This is for #1884, and is a re-wiring of #1885.
The initial problem that #1885 solved was that if you used the
:as
option, translation just didn't happen:Unfortunately, to do so #1885 added a lot of duplicated code. This PR is an attempt to find a middle ground.
I had to create my own
translate
method, because for some reasonString#human
wasn't properly respectingi18n_key
and theactiverecord.models
I18n scope.But the result is that now you can rename a resource:
and can have custom translations for
Bar