Configure default severity

[Bobronium]

I'm trying to configure default rules severity, but I guess, it doesn't work like that:

    "markdownlint.config": {
        "default": {
            "severity": "Information"
        },
    },

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

const diagnostic = new vscode.Diagnostic(range, message, vscode.DiagnosticSeverity.Warning);

Can we make it configurable?

[DavidAnson]

Why do you want this? The current use of Warning seems appropriate according to the VS Code definitions:

	/**
	 * 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
	}

[Bobronium]

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.

[DavidAnson]

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

[Bobronium]

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

[amyq]

As a technical writer, I'm interested in this too, and can unpack why. The technical writers at GitLab use markdownlint as part of our linting suite. For rules that we enable, violations cause the docs-lint markdown job to fail in CI/CD. Thus, for us any Markdownlint findings are errors and not warnings.

The Problems output in VS Code sorts by severity, so it would be nice to surface these as we do any other error.

We do have a pre-push hook set up that fails when Markdownlint findings are detected, but it would be nice if the findings were flagged as errors in the editor.

[jmskarda]

Why do you want this? The current use of Warning seems appropriate according to the VS Code definitions:
...

I also would appreciate the ability to customize the severity assigned to Markdown linting issues. Most of the teams that I work on don't have a style guide for Markdown. Every Markdown file that I open has linting issues. Classifying them as "Warning" causes the tab to turn yellow, a color I prefer to reserve for more serious issues:

My VS Code Severity Strategy:

• Error (red tab): Compile errors that must be fixed
• Warning (yellow tab): Code issue that might work but is confusing, ambiguous, or likely incorrect
• Information (tab normal color, blue inline text underline): Violations of style or best practices
• Hint (tab normal color, gray inline text underline): I don't use this setting because VS code displays them in a way that is too subtle for me to notice.

I prefer to classify Markdown linting issues as "information" instead of as "warning". I want to see them underlined in blue so that I can fix them. I will do so if they are in a section that I am writing, but I usually won't fix them in existing portions of the document that other developers have written. In many cases its just a difference in style preference. VS Code's warning severity is displayed a too "loudly" in the UI for mere Markdown linting issues. It's a color I reserve for more serious issues.