Kyle Simpson

It's too slippery of a slope. We add an exception for "if a type is present" and then someone wants "well, if the type is like this __". I am...

More generally, my reaction to requests to add exceptions for the `where` of using arrow functions in various contexts is... it seems like mostly, people want to use arrows as...

> I think arrow functions are fine when assigned to a variable with a type declaration. To address this opinion, explicitly: I respect your opinion here, but I very much...

> The inability to declare the type of a function declaration is... This is legal in TS, AFAICT: ```js function isNullish(value: unknown): Boolean { return value == null; } ```...

> As long as that is allowed... If I understand you correctly, you're asking about this function form? ```js const isNullish: Predicate = function (value) { return value == null;...

> I would still prefer more pragmatic approach Several features/modes of this rule-plugin have been added after extensive discussion and lobbying by users. I am pragmatic enough to be willing...

The way to contribute on this particular issue is to help collect information on what particular arrangement of config settings would be good as a preset default. There's one config...

We'll have multiple presets... One will be "getify-says", but then yes we'll name the other presets according to their purpose or intended environment.

**NOTE:** I think this may be better as its own standalone plugin/rule, instead of only applying to arrow functions (in this "proper-arrows" plugin).

14 of the PARENS tests are failing, as indicated here: https://travis-ci.org/getify/eslint-plugin-proper-ternary/jobs/656153042 Can you check to see why?