import and build new upstream release 7.2.0

[pve-eslint.git] / eslint / docs / developer-guide / working-with-rules.md

diff --git a/eslint/docs/developer-guide/working-with-rules.md b/eslint/docs/developer-guide/working-with-rules.md
index 608a38be7bc89fff8b3ed6eb21f40ebf37f31687..17058b4058af92d6c96f489ed4799b4c2d85358f 100644 (file)
--- a/eslint/docs/developer-guide/working-with-rules.md
+++ b/eslint/docs/developer-guide/working-with-rules.md
@@ -140,7 +140,7 @@ Additionally, the `context` object has the following methods:
     * Otherwise, if the node does not declare any variables, an empty array is returned.
 * `getFilename()` - returns the filename associated with the source.
 * `getScope()` - returns the [scope](./scope-manager-interface.md#scope-interface) of the currently-traversed node. This information can be used to track references to variables.
-* `getSourceCode()` - returns a [`SourceCode`](#contextgetsourcecode) object that you can use to work with the source that was passed to ESLint.
+* `getSourceCode()` - returns a [`SourceCode`](#context-getsourcecode) object that you can use to work with the source that was passed to ESLint.
 * `markVariableAsUsed(name)` - marks a variable with the given name in the current scope as used. This affects the [no-unused-vars](../rules/no-unused-vars.md) rule. Returns `true` if a variable with the given name was found and marked as used, otherwise `false`.
 * `report(descriptor)` - reports a problem in the code (see the [dedicated section](#context-report)).