This should hopefully prevent issues such as #2563 in the future.

• feat(helpers)!: stricter checking for function signature passed to multiple #2563

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.57%. Comparing base (a536a9d) to head (e6007f2).

@@            Coverage Diff             @@
##             next    #2722      +/-   ##
==========================================
- Coverage   99.57%   99.57%   -0.01%     
==========================================
  Files        2859     2859              
  Lines      248602   248602              
  Branches      630      989     +359     
==========================================
- Hits       247557   247538      -19     
- Misses       1016     1035      +19     
  Partials       29       29              

I agree with the comments from @xDivisionByZerox and @matthewmayer here.
Enabling this rule harms code readability/adds unnecessary boilerplate to it.
I also considered adding an option to it, allowing for single argument parameters, but methods can be re-assigned without optional parameters without actually stripping them, so this would break the intention of the rule:

const fn: (arg1): T = (arg1, arg2?): T => { ...}
// fn still takes the second argument, although sneakily
return array.map(fn);
// would not show an error because the method type only takes a single argument

For this reason, this PR disables the rule permanently.