Fix issue IDs for ReferentialEquality and DoubleMutability#4040
Conversation
schalkms
left a comment
There was a problem hiding this comment.
Thanks for the fix! I guess this strings were forgotten during the rule refactoring.
Codecov Report
@@ Coverage Diff @@
## main #4040 +/- ##
=========================================
Coverage 83.56% 83.57%
- Complexity 3182 3186 +4
=========================================
Files 459 459
Lines 9092 9097 +5
Branches 1771 1772 +1
=========================================
+ Hits 7598 7603 +5
Misses 561 561
Partials 933 933
Continue to review full report at Codecov.
|
|
@schalkms Np! :) How do I get this merged? |
|
@geojakes I think the following issue needs to be fixed. Then this PR is ready to be merged. |
|
@schalkms Looks like that's unrelated to the PR since that area isn't being touched at all. I ran a detektMain and detektTest on the repo, seems like there are many more locations with the same issue |
|
@schalkms Made the relevant changes to that specific file though |
Yes, this is kind of unrelated to this PR. However, the fixed rule now yields errors for the detekt codebase, since detekt's static analysis capability is applied to itself. This approach is also called dogfooding. |
|
@schalkms Looks like once that is fixed, it yielded more errors These look a little more complicated to fix. Maybe we should turn this rule off and open a new issue to address the same? |
|
Updated to disable the rule, adding a new issue to fix the same: #4042 |
|
Looks like this scan is broken in the main branch as well... |
BraisGabin
left a comment
There was a problem hiding this comment.
Good catch! But... This seems like an issue in the config generation... We should use the issue name, no the class name.
|
@BraisGabin I somehow get weird outputs from the repo. When I apply my fix, it picks up the DoubleMutability issues, but does allow me to deactivate it from the config. On the other hand, another project that I work on, runs 1.18.0, picks up the DoubleMutability issue, but does not allow deactivation via config. Is this because of how detekt does its dogfooding? |
|
No, no, your fix is perfect. But I think that we could fix the generator to prevent this kind of issues. But that's another topic. |
|
@schalkms @BraisGabin Does this look okay to merge? |
|
It does. |
|
@BraisGabin What is the process for a micro version release? |
|
There is not a defined process or ETA. But this kind of fix versions are released "fast" |
Trying to fix for #4039
I think the issue ID created does not match the configuration and hence does not affect it the same way as expected.
Disabling the DoubleMutabilityForCollection rule as it seems the project has quite a few of said issues