Made diagnosticSeverityOverrides use clearer + added links to and fro

docs/configuration/config-files.md

@@ -115,7 +115,7 @@ The following settings control pyright’s diagnostic output (warnings or errors
 
 ### Type Check Rule Overrides
 
-The following settings allow more fine grained control over the **typeCheckingMode**. Unless otherwise specified, each diagnostic setting can specify a boolean value (`false` indicating that no error is generated and `true` indicating that an error is generated). Alternatively, a string value of `"none"`, `"hint"`, `"warning"`, `"information"`, or `"error"` can be used to specify the diagnostic level. [see above for more information](#diagnostic-categories)
+The following settings allow more fine grained control over the **typeCheckingMode**. Unless otherwise specified, each diagnostic setting can specify a boolean value (`false` indicating that no error is generated and `true` indicating that an error is generated). Alternatively, a string value of `"none"`, `"hint"`, `"warning"`, `"information"`, or `"error"` can be used to specify the diagnostic level. [see above for more information](#diagnostic-categories), and check the [language server discouraged settings](./language-server-settings.md#discouraged-settings) to learn how to use them in your config (note that as the name implies and as explained in this aforementioned section, you should avoid doing that in your editor's main config).
 
 - <a name="reportGeneralTypeIssues"></a> **reportGeneralTypeIssues** [boolean or string, optional]: Generate or suppress diagnostics for general type inconsistencies, unsupported operations, argument/parameter mismatches, etc. This covers all of the basic type-checking rules not covered by other rules. It does not include syntax errors.
 

docs/configuration/language-server-settings.md

@@ -106,7 +106,12 @@ the basedpyright language server settings can be configured using a workspace or
 
 ```json title="./.vscode/settings.json"
 {
-    "basedpyright.analysis.diagnosticMode": "openFilesOnly"
+    "basedpyright.analysis.diagnosticMode": "openFilesOnly",
+    "basedpyright.analysis.typeCheckingMode": "standard",
+    "basedpyright.analysis.diagnosticSeverityOverrides": {
+        "reportCallIssue": "warning",
+        "reportArgumentType": false
+    }
 }
 ```
 
@@ -120,6 +125,11 @@ require("lspconfig").basedpyright.setup {
     basedpyright = {
       analysis = {
         diagnosticMode = "openFilesOnly",
+        typeCheckingMode = "standard",
+        diagnosticSeverityOverrides = {
+            reportCallIssue = "warning",
+            reportArgumentType = false
+        },
         inlayHints = {
           callArgumentNames = true
         }
@@ -138,6 +148,9 @@ args = ["--stdio"]
 
 [language-server.basedpyright.config]
 basedpyright.analysis.diagnosticMode = "openFilesOnly"
+basedpyright.analysis.typeCheckingMode = "standard"
+basedpyright.analysis.diagnosticSeverityOverrides.reportCallIssue = "warning"
+basedpyright.analysis.diagnosticSeverityOverrides.reportArgumentType = false
 ```
 
 ### zed
@@ -156,7 +169,12 @@ basedpyright.analysis.diagnosticMode = "openFilesOnly"
                     "pythonPath": ".venv/bin/python"
                 },
                 "basedpyright.analysis": {
-                    "diagnosticMode": "openFilesOnly"
+                    "diagnosticMode": "openFilesOnly",
+                    "typeCheckingMode": "standard",
+                    "diagnosticSeverityOverrides": {
+                        "reportCallIssue": "warning",
+                        "reportArgumentType": false
+                    }
                 }
             }
         }

pyproject.toml

@@ -124,6 +124,7 @@ load-plugins = [
 disable = ["R", "C", "E", "F", "W", "I"]
 enable = [
     "useless-suppression",
+    "fatal",
     # rules that have not yet been implemented in ruff. once all of these are implemented in ruff, we should remove pylint
     # (see https://github.com/astral-sh/ruff/issues/970):
     "access-member-before-definition",