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
The IDEA plugin allows to configure - maybe even detect automatically by convention - baseline files for each module individually to match the behavior of the baseline create task that does not support merged findings (detekt/detekt#5712 (comment)).
Current Behavior
It is possible to configure one merged baseline file in the IDEA plugin that can be updated from findings via quick actions from any module in the project (updating <ManuallySuppressedIssues/>), but when the detektBaseline is run on a multi module project where each module is configured to match the configuration options of the IDEA plugin the last module wins and we end with an empty <CurrentIssues /> block.
Running then detekt in the project leads to many findings across the different modules.
Context
We are refactoring a project into different modules - including moving and renaming of classes - and manually suppressing each issue while doing so is not really feasible and rather counterintuitive.
I'd also prefer to have each module to have its own configuration files as it's easier to maintain.
The text was updated successfully, but these errors were encountered:
Expected Behavior
The IDEA plugin allows to configure - maybe even detect automatically by convention - baseline files for each module individually to match the behavior of the baseline create task that does not support merged findings (detekt/detekt#5712 (comment)).
Current Behavior
It is possible to configure one merged baseline file in the IDEA plugin that can be updated from findings via quick actions from any module in the project (updating
<ManuallySuppressedIssues/>
), but when thedetektBaseline
is run on a multi module project where each module is configured to match the configuration options of the IDEA plugin the last module wins and we end with an empty<CurrentIssues />
block.Running then
detekt
in the project leads to many findings across the different modules.Context
We are refactoring a project into different modules - including moving and renaming of classes - and manually suppressing each issue while doing so is not really feasible and rather counterintuitive.
I'd also prefer to have each module to have its own configuration files as it's easier to maintain.
The text was updated successfully, but these errors were encountered: