We'll want to ensure that bulk suppression is also respected in editor extensions / LSP. We should add integration tests to check that diagnostics are still available in editors when bulk suppressions are being used. Ideally we don't render this the same as normal diagnostics though: we should render it more subtly. For example: #19791. That way developers are still aware of suppressed errors and are encouraged to fix them, but it's not as distracting as new errors added to the code.
As a bonus, it would be neat to have another alternative code action to the // oxlint-disable comments that automatically adds a bulk suppression for just that rule violation in the suppression file.
We'll want to ensure that bulk suppression is also respected in editor extensions / LSP. We should add integration tests to check that diagnostics are still available in editors when bulk suppressions are being used. Ideally we don't render this the same as normal diagnostics though: we should render it more subtly. For example: #19791. That way developers are still aware of suppressed errors and are encouraged to fix them, but it's not as distracting as new errors added to the code.
As a bonus, it would be neat to have another alternative code action to the
// oxlint-disablecomments that automatically adds a bulk suppression for just that rule violation in the suppression file.