prefer-spread doesn't report Reflect.apply calls.

Tell us about your environment

• ESLint Version: 3.8.1
• Node Version: v6.9.0
• npm Version: 3.10.8

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

rules:
  prefer-spread: 2

What did you do?

From the example:

foo.apply(null, args);

One of my coworkers has decided to refactor this sort of syntax using Reflect instead of spread params.

Reflect.apply(foo, null, args);

What did you expect to happen?

I would expect prefer-spread to not accept this syntax either, enforcing my coworkers to use the spread syntax. At least I think it should be possible to enforce this using a setting.

What actually happened? Please include the actual, raw output from ESLint.

Eslint didn’t report anything.

[nzakas]

Our standard operating procedure is to keep rules as small as possible. The argument that “it won’t hurt to have it in the rule” only leads to large rules that are hard to maintain. Since in this case it looks like there is another way to accomplish the same thing, it seems like not updating the rule for this specific case is the best case forward.

[kaicataldo]

Closing this issue as it looks like a sufficient workaround was suggested and it doesn’t look like there’s enough support to pursue an enhancement of the rule.