feat(language_server): use linter runtime

[Sysix]

closes #7118

Added tests for:

• (language_server & VSCode) nested configuration
• (language_server & VSCode) nested configuration extends
• (language_server) without nested configuration

The implementation requires at the moment a feature flag for oxc_linter. I added documentation in runtime.rs to let others know why this is needed. Maybe someone can refactor it to avoid the flag. My first idea is a Trait for file system, but you guys know what to do <3

[Sysix]

• perf(langage_server): prebuild IsolatedLintHandler #10406
• feat(language_server): use linter runtime #10268 👈 (View in Graphite)
• fix(language_server): diable nested configuration when config path is provided #10385
• test(editor): refactor tests to use fixtures #10381
• main

---

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.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #10268 will not alter performance

_{Comparing 04-06-feat_language_server_use_linter_runtime (bb8a078) with main (0a42695)}

Summary

✅ 36 untouched benchmarks

[camchenry]

Just commenting here to say I think this is generally the right direction: we should use the same runtime as oxlint, which should also enable us to use the cross-module analysis for import plugin and such. We'll probably need to implement a walker for getting all lintable files though. Then, the other hard part is determining which files need to be re-linted based on which file was saved.

[Sysix]

We'll probably need to implement a walker for getting all lintable files though. Then, the other hard part is determining which files need to be re-linted based on which file was saved.

I thought about that. My preferred way is to handle it inside the runtime.
When oxlint uses a command like npx oxlint /some/deep/folder/ and the files inside using imports like ../<filename> we should still analyze them.
We can give the runtime with the paths a good hint to pre-work the files, but I do not think we can solve that completely without reading files when needed.
I found already some code in the runtime to diff between only semantics vs lint files. Maybe the goal to it is not so far away.

[Boshen]

I'll test and release the lsp changes before merging this.

[graphite-app]

Merge activity

• Apr 16, 2:58 AM EDT: Boshen added this pull request to the Graphite merge queue.
• Apr 16, 3:06 AM EDT: Merged by the Graphite merge queue.