feat(oxc_language_server): implement oxc.fixAll workspace command

[marekvospel]

This pull request focuses on optimizing the implementation of the oxlint.applyAllFixesFile vscode command by adding the command interface to the LSP instead of requesting all code actions and executing the preferred ones. This PR contains an abstraction above the LSP workspace commands, the oxc.fixAll command itself and minor changes to the vscode extension.

Since the workspace/executeCommand handler is new, I've created an abstraction to register the commands and parse their arguments. While it isn't necessary, I feel like it makes future additions to the LS easier.

I tested the command in both vscode and neovim, doubt it will be hard to use this in the zed / intellij projects.

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[marekvospel]

I've added some notes that I'd like to have your input on 😀

[Sysix]

Nice work. I could not test it (see one discussion) but from the outside this looks great 👍

[marekvospel]

@Sysix
I tested the code on the default vscodium installation on nixos and the command worked.

Do you perhaps have oxlint installed in the project you are testing in? The vscode extension prefers the binary in node modules if available. (Resulting in Method not found error. - This is not optimal, but I'm not sure how to handle this other than creating an issue that users can find telling them to update oxlint to latest)

The commands in package.json are only the CTRL + Shift + P commands, not the LSP ones (at least from what I know)

[Sysix]

The commands in package.json are only the CTRL + Shift + P commands, not the LSP ones (at least from what I know)

How do I tell vscode to execute the LSP Command?

Do you perhaps have oxlint installed in the project you are testing in?

Yes. But it still works (somehow). I printed the vscode ClientCapability with this method for you.

[marekvospel]

The commands in package.json are only the CTRL + Shift + P commands, not the LSP ones (at least from what I know)

How do I tell vscode to execute the LSP Command?

Do you perhaps have oxlint installed in the project you are testing in?

Yes. But it still works (somehow). I printed the vscode ClientCapability with this method for you.

I don't think that you can directly exefute the LSP command without the use of a plugin. It's more like an interface for an editor to use - This PR updates the vscode command to use the new LSP command, so if the fix all (file) command works as intended with the latest build, it should be working.

[Sysix]

Thanks for the explanation. I tested this command. worked!

[codspeed-hq]

CodSpeed Performance Report

Merging #8858 will not alter performance

_{Comparing marekvospel:lsp-fix-all-command (04db8e0) with main (d6d80f7)}

Summary

✅ 33 untouched benchmarks

[Sysix]

thanks you. there can probably be more optimization done in this package.