-
-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix typo: function is missing closing parenthesis #585
Fix typo: function is missing closing parenthesis #585
Conversation
Fixes typo for 'store_translations' function - issue ruby-i18n#575
# rule: { | ||
# 'ü' => 'ue', | ||
# 'ö' => 'oe' | ||
# } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why rubocop sees this hash with '=>' syntax as valid.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As valid or invalid?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As valid, as far as I understand, rubocop should shout at me to change this but it actually does not do it and maybe it's because of multi-level nesting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@radar so WDYT, should we stick to the rubocop convention and add something like this:
# store_translations(:de, i18n: {
# transliterate: {
# rule: {
# 'ü': 'ue',
# 'ö': 'oe'
# }
# }
# })
or maybe stick to the existing convention like that:
# store_translations(:de, :i18n => {
# :transliterate => {
# :rule => {
# "ü" => "ue",
# "ö" => "oe"
# }
# }
# })
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing Rubocop doesn't mind if it's a string or a symbol in this case because it's not an ascii character. I don't know the exact reason, and I don't have a preference for one over the other.
Fixes typo for 'store_translations' function - issue #575