Nitin Kumar comments

Results 221 comments of


                                            Nitin Kumar

Bug: [flat config] ESLint continues linting files after an error occurs

I'll look into it.

feat: ignore IIFE's in the `no-loop-func` rule

>The only downside is that this can change error locations (and thus existing `eslint-disable-next?-line` comments would have to be reallocated) and the total number of errors if there are multiple...

feat: ignore IIFE's in the `no-loop-func` rule

Makes sense, I'll update the PR 👍🏻

feat: ignore IIFE's in the `no-loop-func` rule

@mdjermanovic Thanks for the detailed review, I've resolved and added corresponding test cases to your comments.

Change Request: Add "did you mean" for slightly incorrect rule option keys

I'd be okay with this change as this improves DX. We can do either of the following: 1. There is another popular package [`fastest-levenshtein`](https://www.npmjs.com/package/fastest-levenshtein) which we can leverage and it's...

Rule Change: allow `void` in `array-callback-return` for `Array.prototype.forEach`

@Tanujkanti4441 feel free to work on this.

Bug: inline rule overrides via eslint-disable-next-line are ignored during linting

No response, hence closing.

Rule Change: no-shadow with ignoreOnInitialization should allow nested callbacks

I also feel that the current behavior is fine 👍🏻

Bug: Configuration that throws an error with an immutable message will crash ESLint with useless error

@6XGate This seems to be fixed in the [new configuration system](https://eslint.org/docs/latest/user-guide/configuring/configuration-files-new). I'm not sure if we would want to fix it in the current config system. @nzakas WDYT? ### Old...

init abandoned?

No response. Hence closing.