Diagnostic severity as "warning" for linting rules and "error" for parsing errors about vscode-sqlfluff HOT 2 CLOSED

@Jonathan-MW You can change the setting sqlfluff.linter.diagnosticSeverity to adjust the default to warning instead of error. Then change the sqlfluff.linter.diagnosticSeverityByRule to alter the parsing errors to be red error problems instead of warnings.

"sqlfluff.linter.diagnosticSeverity": "warning",
"sqlfluff.linter.diagnosticSeverityByRule": [
    {
      "rule": "PRS",
      "severity": "error"
    }
  ],

from vscode-sqlfluff.

Thanks!
I also found that some extra linting rules need to be defined with severity: "error".
E.g. L038, as a comma after the last column definition in a select statement does throw an error for the sql engine I used (Databricks/spark sql). However Sqlfluff does not throw an "unparsable" error for this trailing comma (only the L038 violation), even though the sql dialect is set to "databricks" in the vscode settings ("sqlfluff.dialect": "databricks").

from vscode-sqlfluff.