Robocop uses plugin-like architecture where rules and reports act as plugins. They are dynamically discovered on start and loaded. If rule or report is not enabled it is not loaded at all (it could be changed recently for rules only - need to verify). That means if someone tries to configure report that is not enabled, it will fail with 'report does not exist' exception:
robocop --configure sarif:output_dir:src .
It should not affect the performance to have everything loaded - rules/reports can be filtered in runtime depending on the enabled status. Additional advantage is that it could make it possible to have multiple configuration files (depending on the dir) same as robotidy.
Robocop uses plugin-like architecture where rules and reports act as plugins. They are dynamically discovered on start and loaded. If rule or report is not enabled it is not loaded at all (it could be changed recently for rules only - need to verify). That means if someone tries to configure report that is not enabled, it will fail with 'report does not exist' exception:
It should not affect the performance to have everything loaded - rules/reports can be filtered in runtime depending on the enabled status. Additional advantage is that it could make it possible to have multiple configuration files (depending on the dir) same as robotidy.