add

Signed-off-by: A.Arnold <[email protected]>

Author: anarnold97

docs/topics/yaml-rule-structure-syntax.adoc

@@ -431,6 +431,7 @@ java.referenced:
   pattern: java.util.List
 ----
 
+=====
 ====== `java` locations
 
 The Java provider allows scoping down the search to certain source code locations. You can scope down Java searches from any one of the following search locations:
@@ -519,35 +520,6 @@ In the current release of {ProductShortName}, fully qualified static method matc
 * *CLASS* (declaration): matches against a given method declaration. It can be coupled with an annotation match.
 
 
-
-// Module included in the following assemblies:
-//
-// * docs/rules-development-guide/master.adoc
-
-:_mod-docs-content-type: REFERENCE
-[id="yaml-custom-variables_{context}"]
-= Custom variables
-
-Provider conditions can have associated custom variables. You can use custom variables to capture relevant information from the matched line in the source code. The values of these variables are interpolated with data matched in the source code.
-
-These values can be used to generate detailed template messages in a rule's action (see xref:yaml-rule-actions_{context}[Message actions]). They can be added to a rule in the `customVariables` field:
-
-[source,yaml]
-----
-- ruleID: lang-ref-004
-   customVariables:
-   - pattern: '([A-z]+)\.get\(\)' # <1>
-      name: VariableName # <2>
-    message: "Found generic call - {{ VariableName }}" # <3>
-  when:
-      java.referenced:
-          location: METHOD_CALL
-          pattern: com.example.apps.GenericClass.get
-----
-<1> `pattern`: A regular expression pattern that is matched on the source code line when a match is found.
-<2> `name`: The name of the variable that can be used in templates.
-<3> `message`: A template for a message using a custom variable.
-
 ===== `go` provider
 
 The `go` provider analyzes Go source code. This provider's capabilities are `referenced` and `dependency`.