Automatically suppress linter errors

[allanlewis]

As per my Discord thread, I'd love to see something similar to Ruff's --add-noqa option, which adds linter-suppressing comments for each error.

My standard workflow when adding Ruff to an existing Python codebase is to run:

ruff check --fix
ruff check --add-noqa
ruff check

This fixes all safely-fixable errors, suppresses the rest, and then checks that there are no remaining errors. Perhaps we could enable a similar workflow in Biome?

Aside, one thing that might make this easier would be if the JSON output (biome lint --reporter=json) gave the line number of each error rather than the character number, then one could use sed or similar to insert suppression comments.

[ematipico]

Out of curiosity, what does noqa stand for? I don't know python and its ecosystem

[nhedger]

My guess is no quality assurance

[allanlewis]

Yes, "noqa" means "no quality assurance", it comes from one of the early Python linters and has been adopted by Ruff.

[anthonyshew]

Working on this feature here!: #4007

[eMerzh]

i was wondering if by doing that we couldn't migrate eslint comments to biome 🤔
it's not exactly the same, but it looks like there are some common stuff

[ematipico]

That's out of scope for this proposal.

Plus, it isn't possible to map all kinds of Eslint suppression comments to Biome

[anthonyshew]

I'll also add: As I'm converting to Biome, I remove some rule in ESLint and then ESLint complains about an unused ignore comment. Running ESLint with --fix removes the comment. Pretty quick to get rid of the unneeded comments with ESLint itself!