Allow configuring suppressions/unused rule fix

[kymckay]

Currently the suppressions/unused rule flags as an unsafe fix. I'd love to be able to configure the rule fix to be considered safe so that these automatically get cleaned up.

For clarity: it seems like this rule specifically is not configurable in biome.json.

[ematipico]

There's some misunderstanding.

suppression/unused isn't the name of a rule, it's the category of the diagnostic.

That's not a lint rule, and I believe there's no code action (fix) associated with it.

Given that, what kind of resolution/proposal are you looking for? Can you be more specific about your idea and provide more examples?

[kymckay]

Fast response! Yep, can explain the misunderstanding too 😄 This

The icon ⚠ indicates that the rule provides a code action (fix) that is unsafe to apply.

in the docs made me think there was an unsafe fix suggested when I saw the same symbol in the CLI.

I'm in the process of migrating a codebase over from ESLint and as part of that some of the old suppression statements (which I've just replaced in bulk) no longer apply. My thinking was that it'd be nice to configure Biome to strip such unused suppression statements out, because it's already doing the work of detecting that they're unused.

[GRA0007]

Adding to this, I'd like at least the ability to see a list of all unused suppression comments in the codebase. Using biome lint --summary shows that I have 22 with the rule name suppressions/unused, but I can't find any option to filter the output so I get a list of files with these warnings. We have a very large codebase with lots of other warnings at the moment, and when we change our Biome config or refactor code, we often get unused suppression comments.

[ematipico]

Yes, that's on my radar too.

Having a better suppression system inspired by elm-review.

We'll get to that eventually