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
Hmm, I think someone else already raised this issue once. I'm not sure I was us to introduce special handling for just a single scenario. Maybe that would make sense if there are other methods expecting a constant referred by a symbol. Or maybe we should this case since it various scenarios snake_case, camelCase (generally when producing json for web APIs), PascalCase and SCREAMING_SNAKE_CASE is employed.
There are many situations in which it is necessary to use symbols that are not snake case, and the normal way of getting rid of the reports will have to be turning off the SymbolName cop locally with comments or configuration files. However, since this case is related to a feature in Ruby and not to a particular application, I think it's reasonable to implement special handling of it in RuboCop.
Example :
raises :
The text was updated successfully, but these errors were encountered: