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
Originally posted by richdapice January 26, 2022
I recently upgraded to 1.19.0 and updated my rules as well, although I already had SpacingBetweenPackageAndImports and MaxLineLength and they were both active.
I am able to generate a baseline file after deleting the previous baseline I see it being created. The problem is, after generating the baseline I run my check but I fail for issues that ARE IN the baseline.
I have checked my detekt configuration multiple times and wasn't having this issue before the update.
I am failing the check locally and as a GitHub action.
Maybe we should revert #4335. This was kind of a best effert to allow auto-format the baseline but we know that not any format is supported by detekt right now.
Expected Behavior
SpacingBetweenPackageAndImports
issues that are added to the baseline should not fail when running detekt.Observed Behavior
The issue is in the baseline
<ID>SpacingBetweenPackageAndImports:HttpClient.kt$ </ID>
But the check fails for the issue
SpacingBetweenPackageAndImports - [HttpClient.kt]
Steps to Reproduce
Your Environment
Version of detekt used: 1.19.0
Version of Gradle used (if applicable): 7.0.4
Discussed in #4532
Originally posted by richdapice January 26, 2022
I recently upgraded to 1.19.0 and updated my rules as well, although I already had
SpacingBetweenPackageAndImports
andMaxLineLength
and they were both active.I am able to generate a baseline file after deleting the previous baseline I see it being created. The problem is, after generating the baseline I run my check but I fail for issues that ARE IN the baseline.
I have checked my detekt configuration multiple times and wasn't having this issue before the update.
I am failing the check locally and as a GitHub action.
Thanks!
Links
Caused by #4335
Related to #4504
The text was updated successfully, but these errors were encountered: