Hello rubofriends. Is there a way to disable an entire family/group/namespace of cops for a particular set of files?
For example, in my project, I want to disable all "Metrics" cops for my tests, but keep them enabled for all other code. I could just disable each Metrics cop for the test files as the violations pop up, but I want to see if this functionality already exists or requires a new feature.
Okay, the correct term was "department", according to the documentation. So, the "Metrics" department.
Also, I think I just discovered that it is indeed already existing, I was able to just use Metrics:... in my YAML and it worked. Still, not entirely sure if this is the correct approach because I can't find this case mentioned in the docs.
The think is that we want to write it like
def file_params
params
.require(:file)
.permit(
:description,
:user_id,
:content_type,
:created_at,
:updated_at,
:unit_id,
:document_id,
:document_type,
:sort_id,
:is_deleted
)
endI know I could write it on one line but we want to have it like this.
In generall we think to 10 lines method like is good. For some controllers we have more then 10 parameters and need more then 10 lines.
I've seen the list in the code, and in the docs: https://github.com/rubocop-hq/rubocop/blob/master/manual/configuration.md#severity
But I'm curious to when to use what. In particular, is "error" supposed to be used only when RuboCop encounter an internal error processing?
Bit of an out there idea I'd be interested in a sanity check on. Javascript has the idea of codemods, I kinda want to try and make the same thing in Ruby. Rubocop already has a lot of work done on top of parser, including the NodePattern syntax and autocorrect capabilities.
Is there a possibility of generalizing the autocorrect capability into a code rewrite gem?
For example I want to write a cop that creates an offence if anyone sends the method
expiry_date to and instance of Quote object object.Can anyone point in the direction of an example of how to write a cop that can check the class of the object getting the method sent to it?
You can see this being a challenge even for IDEs like RubyMine or VSCode with Ruby+Solargraph extensions. They tend to make use of YARD to pick up types from doc comments to aid the static analysic. But they also have to analyse the whole project to have chance. If you have good YARD comments you could try to leverage that in your custom cops.
expiry_date in the Quote object? because it seems more reasonable than try to create a linter for it. Make the interface fail or warn developers about it. When they run tests they will know the api is no longer going to support it.