Document deep_interpolation
parameter for bulk lookups
#34309
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.
Bulk lookups are sort of an edge case, I have not heard of them until a colleague of mine decided to dynamically iterate over a growing set of translations and receiving them in bulk as a hash with
I18n.t 'welcome'
as in the added example of the guide.When passing an interpolation to these bulk lookups, they will only be performed when also passing
deep_interpolation: true
.Without passing
deep_interpolation
flag:With passing
deep_interpolation
:I found this digging in the I18n lookup backend, the flag is listed on I18n's Rubydoc but not otherwise listed. Since bulk lookups are mentioned here, I suggest to add a note with this flag along with it.
[ci skip]