-
-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure default severity #241
Comments
Why do you want this? The current use of /**
* Represents the severity of diagnostics.
*/
export enum DiagnosticSeverity {
/**
* Something not allowed by the rules of a language or other means.
*/
Error = 0,
/**
* Something suspicious but allowed.
*/
Warning = 1,
/**
* Something to inform about but not a problem.
*/
Information = 2,
/**
* Something to hint to a better way of doing it, like proposing
* a refactoring.
*/
Hint = 3
} |
I'm not saying it's wrong in any way. It's usually configurable in other linters (pyright, etc.) and it gives certain flexibility when configuring a bunch of plugins/theme combo. |
Thanks. What changes if you were able to change these from Warning to Information? Are there different policies that kick in or something? |
It allows in turn to configure a visual scheme for one's taste. For instance: https://github.com/Bobronium/vscode-pycharm-darcula-theme#linting-highlighting |
I'm trying to configure default rules severity, but I guess, it doesn't work like that:
Is there a way to do it?
Upd.
Ok, I see now that severity is hardcoded here:
vscode-markdownlint/extension.js
Line 598 in 522848a
Can we make it configurable?
The text was updated successfully, but these errors were encountered: