About eslint, when you modify one line of code, it may cause eslint to check multiple lines of code. How to optimize at this time?

when we check the code with eslint, there may be such a situation: only one line of code has been changed, but it causes eslint to report a large area of error, so how to make eslint report only one line of code instead of a large area of error? How to optimize eslint?

                                                                --
May.24,2021

this is not scientific. If you think about it, before you change the code, eslint doesn't report anything wrong, you change one line of code, and then eslint reports a lot of errors on other lines, which is obviously caused by you changing this line of code. What does eslint have to do with it? Why optimize eslint? Obviously what you should do is to check what is affecting eslint, in your business, rather than rushing to change eslint settings. Is this a brain teaser trap for the author?


I suspect it's clever, too. Is it a method to change the object? () = > {} change {} ?

-- max-warnings or this is the modification threshold, but warning.

Menu