Valid keys slipping through as invalid and not showing up missing

[keldin-coding]

We had an issue where we had an invalid key used in our views, but we didn't notice until it went to production because it raises a TranslationMissingError.

# Translations
en:
  parent:
    original_value: 'Some text'

# Usage in HAML

%p= t('parent.original_value:')

In this instance, with strict: true, the key is seen as invalid on this line. Because of that, it's never processed. I'm not sure how you would want to handle this. Maybe providing a list of invalid keys and their usage in the application? Letting them go through and be used as missing translation?

As far as I can tell though, I18n allows this kind of key in my testing...

# sample other translation
en:
  parent:
    'some_key:': 'A super special value'

# This evalutes
%p= t('parent.some_key:')

[keldin-coding]

Conceivably a fix for this would be modifying this line to include a : as part of the VALID_KEY_CHARS.

[glebm]

Including : in VALID_KEY_CHARS sounds good to me

[keldin-coding]

Welp. Should've realized it would pick up on those commits, my bad. Got a pull request open, though. :)

[glebm]

Released in v0.9.6!