linter: VSCode stops showing errors after saving until the file is changed again

[ktdd]

What version of Oxlint are you using?

1.14.0

What command did you run?

VSCode extension

What does your .oxlintrc.json config file look like?

Default config.

What happened?

I'm not sure if this is a bug or if it's supposed to work like this, but after saving a file in VSCode oxlint doesn't display any errors until the file is changed again. I save a lot, especially when fixing errors, so it's quite annoying to not see the errors after saving.

If I change "oxc.lint.run" to "onSave", this doesn't happen. Obviously I'd like to keep it on "onType".

[Miodec]

Do you have type aware enabled? Might be a duplicate of an issue i opened aswell: #13479

[ktdd]

Do you have type aware enabled? Might be a duplicate of an issue i opened aswell: #13479

Nope, type aware is not enabled. It does seem like your issue is similar though!

[Miodec]

Do you have type aware enabled? Might be a duplicate of an issue i opened aswell: #13479

Nope, type aware is not enabled. It does seem like your issue is similar though!

Tested again, looks like its not related to type aware!

[Sysix]

The bug was introduced in #13332
The problem here is, depending on the configuration, the diagnostic will be cleared.

#13490 will hopefully fix this 🤞
Need to rewrite some code, so the server does not store the diagnostics twice.
Sorry for this problem >.<

[ktdd]

Absolutely no reason to be sorry for, I think everyone here can relate 😁

[sheikhameen]

"oxc.lint.run" vscode option allows for one of two values: onType or onSave, but not both.
By default, it's set to onType. After changing to onSave and reloading extensions, the extension correctly lints on save, but not on type. I'd like to have it set to run on both, preferably something like: "oxc.lint.run": ["onType", "onSave"]. The option doesn't accept array, only string of either values.