David Anson

Agree, thanks!

Closing in favor of #605.

Link to open issue in VS Code: https://github.com/microsoft/vscode/issues/114741

@XhmikosR, is this still relevant?

See #653 for markdown-it plug-in.

I like that workaround for something that has only seemed to come up once in two years.

FYI, there are no optional rules built into the library. That may be a policy I have to change someday, but so far everything in the library is on by...

Agree this is more like 753. I expect to push changes that implement that tonight.

Why do you want this? The current use of `Warning` seems appropriate according to the VS Code definitions: ```js /** * Represents the severity of diagnostics. */ export enum DiagnosticSeverity...

Thanks. What changes if you were able to change these from Warning to Information? Are there different policies that kick in or something?