Ignore Lints

[elijah-potter]

In conversations I've had about Harper (including in #364), a common request has been the ability to ignore individual lint results. I've avoided tackling this problem until now, since I was concerned it would disincentivize us from fixing false-positives in our rules. Now that we're rolling out more integrations, the context has shifted enough that this is now an important feature.

The Plan

I plan on making significant changes to the harper-core::linting module to make this happen.
The implementation should have a general-enough API that it can be consumed in harper-ls (as a code action), and consumers of harper.js.

We will store each lint to be ignored in a persistent manner, that is compatible with whatever client is consuming Harper.

This PR will remain a draft until completion.

[elijah-potter]

To summarize what I've done:

I've introduced a structure (IgnoredLints) to organize, store and identify lints that have been previously marked as "ignored". I've the Linter type in harper.js (not to be confused with the Rust Linter type) composes IgnoredLints to allow JavaScript consumers to ignore lints in a privacy-respecting way, as well as store those settings as a string.

I then added UI for harper-ls and the Obsidian plugin to allow users to ignore lints. Right now, I've only added persistence to the Obsidian plugin, so if you ignore a lint in harper-ls and reopen the buffer, it will forget.