Support integer keys with string lookup #445
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.
Improves upon #444 by adding support for integer keys in subtree API (e.g.,
I18n.t(:available)[1]
) alongside support for integer keys in the lookup API (I18n.t('available.1')
).(Note: not fully tested beyond the existing test-coverage, I'm not confident the change to
normalize_key
won't break non-Simple
backends in subtle ways.)