search

oxc-project / oxc

⚓ A collection of JavaScript tools written in Rust.
https://oxc.rs
MIT License
12.58k stars 462 forks source link

editor: problem matcher for oxlint errors #6587

Open sschneider-ihre-pvs opened 1 month ago

sschneider-ihre-pvs commented 1 month ago

What version of Oxlint are you using?

0.9.9

What command did you run?

No response

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

No response

What happened?

It would be great if there would be a problem matcher to transfer the found issues to the problems tab

shulaoda commented 1 month ago

I think we have this feature. What are your specific requirements? Could you describe it?

image

sschneider-ihre-pvs commented 1 month ago

If I want a task like a watcher task for the complete codebase for example.

nrayburn-tech commented 1 month ago

Does the language server support something like this? A way to request all issues for the entire workspace?

Is the Problems tab in VS Code the right place for this? From what I can tell, only problems for open files show there. Are there any other plugins that show problems there for files that are not opened?

DonIsaac commented 1 month ago

We'd have to register a problemMatcher capability in our package.json

nrayburn-tech commented 1 month ago

Does the language server support something like this? A way to request all issues for the entire workspace?

Any idea on this @DonIsaac ?

I can probably come up with some workarounds like identifying all files and requesting diagnostics for each, but I’m not sure if there is a better alternative.

nrayburn-tech commented 1 month ago

Does the language server support something like this? A way to request all issues for the entire workspace?

Any idea on this @DonIsaac ?

I can probably come up with some workarounds like identifying all files and requesting diagnostics for each, but I’m not sure if there is a better alternative.

Looking at the problem matcher, this probably isn’t relevant for VS Code, but I do think it is for IntelliJ. I’ll review it some more and make an IntelliJ specific issue when I know some more about it.