docs: clean old examples

Author: ldez

.golangci.reference.yml

@@ -415,11 +415,12 @@ linters:
       # if check-error-free-encoding is set to true and errcheck linter is enabled,
       # it is recommended to add the following exceptions to prevent from false positives:
       #
-      #     linters-settings:
-      #       errcheck:
-      #         exclude-functions:
-      #           - encoding/json.Marshal
-      #           - encoding/json.MarshalIndent
+      #     linters:
+      #       settings:
+      #         errcheck:
+      #           exclude-functions:
+      #             - encoding/json.Marshal
+      #             - encoding/json.MarshalIndent
       #
       # Default: false
       check-error-free-encoding: true

docs/src/docs/plugins/go-plugins.mdx

@@ -50,18 +50,19 @@ If you're looking for instructions on how to configure your own custom linter, t
 1. If the project you want to lint does not have one already, copy the [.golangci.yml](https://github.com/golangci/golangci-lint/blob/HEAD/.golangci.yml) to the root directory.
 2. Adjust the YAML to appropriate `linters-settings.custom` entries as so:
   ```yaml title=.golangci.yml
-  linters-settings:
-    custom:
-      example:
-        path: /example.so
-        description: The description of the linter
-        original-url: github.com/golangci/example-linter
-        settings: # Settings are optional.
-          one: Foo
-          two:
-            - name: Bar
-          three:
-            name: Bar
+  linters:
+    settings:
+      custom:
+        example:
+          path: /example.so
+          description: The description of the linter
+          original-url: github.com/golangci/example-linter
+          settings: # Settings are optional.
+            one: Foo
+            two:
+              - name: Bar
+            three:
+              name: Bar
   ```
 
 That is all the configuration that is required to run a custom linter in your project.

docs/src/docs/plugins/module-plugins.mdx

@@ -31,18 +31,17 @@ plugins:
 ```
 
 ```yaml title=.golangci.yml
-linters-settings:
-  custom:
-    foo:
-      type: "module"
-      description: This is an example usage of a plugin linter.
-      settings:
-        message: hello
-
 linters:
-  disable-all: true
+  default: none
   enable:
     - foo
+  settings:
+    custom:
+      foo:
+        type: "module"
+        description: This is an example usage of a plugin linter.
+        settings:
+          message: hello
 ```
 
 ## The Manual Way
@@ -56,18 +55,17 @@ linters:
 ### Configuration Example
 
 ```yaml title=.golangci.yml
-linters-settings:
-  custom:
-    foo:
-      type: "module"
-      description: This is an example usage of a plugin linter.
-      settings:
-        message: hello
-
 linters:
-  disable-all: true
+  default: none
   enable:
     - foo
+  settings:
+    custom:
+      foo:
+        type: "module"
+        description: This is an example usage of a plugin linter.
+        settings:
+          message: hello
 ```
 
 ## Reference

docs/src/docs/usage/false-positives.mdx

@@ -17,12 +17,13 @@ Otherwise, some linters have dedicated configuration to exclude or disable rules
 An example with `staticcheck`:
 
 ```yaml
-linters-settings:
-  staticcheck:
-    checks:
-      - all
-      - '-SA1000' # disable the rule SA1000
-      - '-SA1004' # disable the rule SA1004
+linters:
+  settings:
+    staticcheck:
+      checks:
+        - all
+        - '-SA1000' # disable the rule SA1000
+        - '-SA1004' # disable the rule SA1004
 ```
 
 ## Exclude or Skip
@@ -33,90 +34,83 @@ Exclude issue by text using command-line option `-e` or config option `issues.ex
 It's helpful when you decided to ignore all issues of this type.
 Also, you can use `issues.exclude-rules` config option for per-path or per-linter configuration.
 
-In the following example, all the reports that contains the sentences defined in `exclude` are excluded:
-
-```yaml
-issues:
-  exclude:
-    - "Error return value of .((os\\.)?std(out|err)\\..*|.*Close|.*Flush|os\\.Remove(All)?|.*printf?|os\\.(Un)?Setenv). is not checked"
-    - "exported (type|method|function) (.+) should have comment or be unexported"
-    - "ST1000: at least one file in a package should have a package comment"
-```
-
 In the following example, all the reports from the linters (`linters`) that contains the text (`text`) are excluded:
 
 ```yaml
-issues:
-  exclude-rules:
-    - linters:
-        - mnd
-      text: "Magic number: 9"
+linters:
+  exclusions:
+    rules:
+      - linters:
+          - mnd
+        text: "Magic number: 9"
 ```
 
 In the following example, all the reports from the linters (`linters`) that originated from the source (`source`) are excluded:
 
 ```yaml
-issues:
-  exclude-rules:
-    - linters:
-        - lll
-      source: "^//go:generate "
+linters:
+  exclusions:
+    rules:
+      - linters:
+          - lll
+        source: "^//go:generate "
 ```
 
 In the following example, all the reports that contains the text (`text`) in the path (`path`) are excluded:
 
 ```yaml
-issues:
-  exclude-rules:
-    - path: path/to/a/file.go
-      text: "string `example` has (\\d+) occurrences, make it a constant"
+linters:
+  exclusions:
+    rules:
+      - path: path/to/a/file.go
+        text: "string `example` has (\\d+) occurrences, make it a constant"
 ```
 
 ### Exclude Issues by Path
 
-Exclude issues in path by `issues.exclude-dirs`, `issues.exclude-files` or `issues.exclude-rules` config options.
-
-Beware that the paths that get matched here are relative to the current working directory.
-When the configuration contains path patterns that check for specific directories,
-the `--path-prefix` parameter can be used to extend the paths before matching.
+Exclude issues in path by `linters.exclusions.paths`, or `issues.exclude-rules` config options.
 
 In the following example, all the reports from the linters (`linters`) that concerns the path (`path`) are excluded:
 
 ```yaml
-issues:
-  exclude-rules:
-    - path: '(.+)_test\.go'
-      linters:
-        - funlen
-        - goconst
+linters:
+  exclusions:
+    rules:
+      - path: '(.+)_test\.go'
+        linters:
+          - funlen
+          - goconst
 ```
 
 The opposite, excluding reports **except** for specific paths, is also possible.
 In the following example, only test files get checked:
 
 ```yaml
-issues:
-  exclude-rules:
-    - path-except: '(.+)_test\.go'
-      linters:
-        - funlen
-        - goconst
+linters:
+  exclusions:
+    rules:
+      - path-except: '(.+)_test\.go'
+        linters:
+          - funlen
+          - goconst
 ```
 
-In the following example, all the reports related to the files (`exclude-files`) are excluded:
+In the following example, all the reports related to the files (`paths`) are excluded:
 
 ```yaml
-issues:
-  exclude-files:
-    - path/to/a/file.go
+linters:
+  exclusions:
+    paths:
+      - path/to/a/file.go
 ```
 
-In the following example, all the reports related to the directories (`exclude-dirs`) are excluded:
+In the following example, all the reports related to the directories (`paths`) are excluded:
 
 ```yaml
 issues:
-  exclude-dirs:
-    - path/to/a/dir/
+  exclusions:
+    paths:
+      - path/to/a/dir/
 ```
 
 ## Nolint Directive