baseline support

[DetachHead]

i understand this may be considered out of scope for this project, but i've had a similar idea to this tool. i wish i could use a baseline file with all the languages / linters that i use without the feature having to be re-implemented for each tool. unfortunately not many tools support it, and many of them seem to only support it in the CLI but not the language server.

it would be nice if lspx could filter diagnostics from all the language servers using generic / configurable baselining logic, along with a CLI that allows you to gather and filter all the diagnostics in your project (either with or without a baseline file), for the purpose of running in your CI.

if this is something you would consider in-scope for this project, i would be happy to try to contribute this feature myself.

[cowboyd]

@DetachHead This is exactly the kind of use-case that lspx is designed for, and why it has internally a "middleware" approach. I had been thinking that we should support having a some sort of plugin architecture for dynamically loading middleware and also adding CLI options.

[taras]

@DetachHead basefile looks like this a tool for ratcheting

[DetachHead]

yeah that sounds like the same idea (i found out today that eslint recently introduced its own version of the same thing)

though it sounds like neither of these solutions have the matching logic or the language server integration that i have in mind, which is what i would like to accomplish here (and what i did with basedpyright).

the way my idea works is that the baseline file stores the column numbers and order of each error code's occurrence in the file, which means it's able to much more accurately guess which instance of the error code is the new one. the language server will also automatically update the baseline file on textDocument/didSave.

baselined errors are also reported as an IDE hint instead of a warning or error: