You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rubocop currently has Naming/AsciiIdentifiers which correctly adds offenses to ruby identifiers (tIDENTIFIER) containing non-ascii characters. I find that the same rigor should be applied to constants (tCONSTANT) as the following are currently not offenses:
classFoöend
moduleFoöend
FOÖ="foo"
Possible Solution:
A new cop: Naming/AsciiConstants which adds offenses to code where non-ascii characters are used in constant declarations (See examples above)
Alternative:
A configuration option for Naming/AsciiIdentifiers to incorporate constants. Offenses would exist for the examples above. However it does not appear that ruby considers constants as identifiers so this option could be misleading.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!
Rubocop currently has Naming/AsciiIdentifiers which correctly adds offenses to ruby identifiers (
tIDENTIFIER
) containing non-ascii characters. I find that the same rigor should be applied to constants (tCONSTANT
) as the following are currently not offenses:Possible Solution:
A new cop:
Naming/AsciiConstants
which adds offenses to code where non-ascii characters are used in constant declarations (See examples above)Alternative:
A configuration option for
Naming/AsciiIdentifiers
to incorporate constants. Offenses would exist for the examples above. However it does not appear that ruby considers constants as identifiers so this option could be misleading.The text was updated successfully, but these errors were encountered: