fix(oxlint/lsp): report diagnostics referencing another file

[Sysix]

Mostly created with GPT5 🤖

[Sysix]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix(oxlint/lsp): report diagnostics referencing another file #16715 👈 (View in Graphite)
• refactor(oxlint/lsp): accept multiple files inside LintRunner #16668
• refactor(oxlint/lsp): use fs as param in TsGoLintState, instead of source text #16667
• refactor(oxlint/lsp): IsolatedLintHandlerFileSystem is now a FxHashMap #16666
• 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 Performance Report

Merging #16715 will not alter performance

_{Comparing 12-10-fix_oxlint_lsp_report_diagnostics_referencing_another_file (e010485) with main (fc96ee0)}

Summary

✅ 4 untouched
⏩ 41 skipped¹

Footnotes

1. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[Sysix]

@camc314 do you know if tsgolint accept tsconfig.json as an input file?
My current problem: file.ts triggers a diagnostics for tsconfig.json file.
The user fixes the diagnostic in tsconfig.json, but there is no re-linting done for the tsconfig.json.
The error will still be shown, even if file.ts or tsconfig.json is modified again.

Another problem: Having 2 TS files reporting the same tsconfig.json diagnostic.
I need probably to lookup how the TS language server is handling this kind of cross-file diagnostics :/

[camc314]

Can I just use this branch?

I think this probably works with SourceOverrides but i would need to test it

[Sysix]

Can I just use this branch?

Sure :) Keep in mind that the VSCode extension does not send didOpen/didChange/didSave notification to the server for now.

oxc/editors/vscode/client/tools/linter.ts

Lines 130 to 142 in da509be

	const supportedExtensions = [
	"astro",
	"cjs",
	"cts",
	"js",
	"jsx",
	"mjs",
	"mts",
	"svelte",
	"ts",
	"tsx",
	"vue",
	];

[Sysix]

Maybe we should wait for the implementation of textDocument/diagnostic. Its response can have related document diagnostics: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#relatedFullDocumentDiagnosticReport

[Sysix]

With related document diagnostics, it will not be shown inside VS Code editor, do not know how other editor handle this :/