From f652f19bd43d187dddfa6b3663b6f96437a41710 Mon Sep 17 00:00:00 2001 From: Shahroq Date: Mon, 20 Apr 2020 11:24:52 +0330 Subject: [PATCH 1/2] Fix: parser interface link --- docs/user-guide/configuring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/configuring.md b/docs/user-guide/configuring.md index cf5fcfd34f..c7832ca950 100644 --- a/docs/user-guide/configuring.md +++ b/docs/user-guide/configuring.md @@ -63,7 +63,7 @@ Setting parser options helps ESLint determine what is a parsing error. All langu By default, ESLint uses [Espree](https://github.com/eslint/espree) as its parser. You can optionally specify that a different parser should be used in your configuration file so long as the parser meets the following requirements: 1. It must be a Node module loadable from the config file where it appears. Usually, this means you should install the parser package separately using npm. -1. It must conform to the [parser interface](/docs/developer-guide/working-with-plugins#working-with-custom-parsers). +1. It must conform to the [parser interface](/docs/developer-guide/working-with-plugins#processors-in-plugins). Note that even with these compatibilities, there are no guarantees that an external parser will work correctly with ESLint and ESLint will not fix bugs related to incompatibilities with other parsers. From bc833d05fc26f837856167a247694a3ccad3c8ee Mon Sep 17 00:00:00 2001 From: Shahroq Date: Tue, 21 Apr 2020 10:32:13 +0330 Subject: [PATCH 2/2] change the link --- docs/user-guide/configuring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/configuring.md b/docs/user-guide/configuring.md index c7832ca950..694d6f4bc2 100644 --- a/docs/user-guide/configuring.md +++ b/docs/user-guide/configuring.md @@ -63,7 +63,7 @@ Setting parser options helps ESLint determine what is a parsing error. All langu By default, ESLint uses [Espree](https://github.com/eslint/espree) as its parser. You can optionally specify that a different parser should be used in your configuration file so long as the parser meets the following requirements: 1. It must be a Node module loadable from the config file where it appears. Usually, this means you should install the parser package separately using npm. -1. It must conform to the [parser interface](/docs/developer-guide/working-with-plugins#processors-in-plugins). +1. It must conform to the [parser interface](/docs/developer-guide/working-with-custom-parsers). Note that even with these compatibilities, there are no guarantees that an external parser will work correctly with ESLint and ESLint will not fix bugs related to incompatibilities with other parsers.