[no-explicit-any] Adding switches for supported options about typescript-eslint HOT 10 CLOSED

Ha ha no problem.

I don't think that more config would be a bad thing, as long as it's easy to keep the current "no anys are okay" functionality.

Considering we cut the rule down 5 lines, it should be fine to add some complexity back :)

from typescript-eslint.

@armano2 I agree. I already have some options in mind, but I won't be able to work on this until after the holidays.

from typescript-eslint.

One such case is typing generic rest parameters / function arguments:

type HigherOrderFn = <TArgs extends any[], TVal>(fn: (...args: TArgs): TVal): TVal

More in Typescript site

from typescript-eslint.

multiple cases that are currently supported

There aren't any individual cases any more, thanks to the new types provided by the parser!
https://github.com/bradzacher/eslint-plugin-typescript/blob/63311f3d0aca0ad93584eef69180862b8ed25bb8/lib/rules/no-explicit-any.js#L28-L33

from typescript-eslint.

Ha! I was doing this from memory...
I probably should stop doing that as this plugin has changed a lot since we moved to the latest typescript parser... anyway... unless I'm missing something (and I apologize if I am... I've been a little busy with a toddler and a new baby on the way) I think this is still a valid request, isn't it? Would be nice to have a little more control over what gets validated vs ignored.

from typescript-eslint.

@weirdpattern we can add configuration

but we have to define first, base on what we want to limit reporting, and by default all options should be enabled :)

from typescript-eslint.

@bradzacher any work on this issue?

from typescript-eslint.

@moulikcipherX - there hasn't been anything done!
it's difficult though because we don't currently have any "cases" so it'll be a bit of work/discussion to decide what should have options.

However right now there hasn't been anyone asking for options (not even +1's on this issue) - so I wouldn't class this as a high priority enhancement

from typescript-eslint.

Seems like this issue is resolved now? :)

from typescript-eslint.

Yep! Thanks for pointing it out @jhnns

from typescript-eslint.