Hello. I spend a little time for testing rubocop integration and see some
problems.
Not sure that is a bug/flaw or it not a problem at all from your point of view.
In general when you work with rubocop you create a configuration file that allow you to enable/disable and configure some checkers.
That configuration files can be really big and usually is placed in root of project repository.
Web interface of reviewboard allow me only disable some checks per integration.
In our case we have a workaround because rubocop allow to place configuration on system level. So I just put config on reviewbot server and it start to work.
But it can be unappropriate if we need different configurations per repositories.
Anyway it solve not all problems because reviewbot start checks per individual files prepared in root of temp directory.
The problem is about checkers that check that directory structure is correct.
Second problem is disabling/enabling checkers based on file path.
For example we can disable some checkers only for feature tests.
Example config partition:
```
RSpec/ExampleLength:
Max: 15
Exclude:
- 'spec/features/**/*_spec.rb'
```
In general that problems can be resolved if reviewbot will check not indivdual files but directory that contains prepared content. Siplest way is just export repository and apply patches. Another way is about export individual files with correct directory structure and place rubocop configuration in that directory too (from repository root or from tool configuration).
Not sure about performance and is it a correct solution for reviewbot architecture.
Is it a reviewbot limitations or bug/flaw?
I think that in other linters there is a similar problems, so I think that it a general question.