Documentation bug in max-depth #11991
Closed
Comments
|
Hi @imai0917, thanks for the issue. You are right: that is not a good example in the docs and it needs to be changed. Would you like to submit a pull request? |
|
However, the default option of |
|
Yeah, I would submit a pull request. The below example would work with the default option
|
imai0917
pushed a commit
to imai0917/eslint
that referenced
this issue
Jul 18, 2019
gabrieldrs
added a commit
to gabrieldrs/eslint
that referenced
this issue
Oct 1, 2019
Signed-off-by: Gabriel R. Sezefredo <g@briel.dev>
Mahesh419
added a commit
to Mahesh419/eslint
that referenced
this issue
Oct 2, 2019
Closed
Mahesh419
added a commit
to Mahesh419/eslint
that referenced
this issue
Oct 2, 2019
gabrieldrs
added a commit
to gabrieldrs/eslint
that referenced
this issue
Oct 2, 2019
Signed-off-by: Gabriel R. Sezefredo <g@briel.dev>
|
Could this be assigned to @imai0917? I was looking for something to take for Hacktober Fest but this is already fixed. |
This was referenced Nov 9, 2019
This was referenced Mar 11, 2020
This was referenced Mar 26, 2020
This was referenced Apr 3, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The version of ESLint you are using.
v5.16.0
The problem you want to solve.
The below example is from https://eslint.org/docs/rules/max-depth, ESLint v5.16.0 doesn't make issues for the example.
Nesting function expressions would not be counted as a nesting depth, so the arrow function expression would not increase the depth count but reset the count.
Your take on the correct solution to problem.
The below example or other equivalents would work.
Are you willing to submit a pull request to implement this change?
The text was updated successfully, but these errors were encountered: