Conflicts between `no-prototype-builtins` and `no-useless-call`

Tell us about your environment

• ESLint Version: 7.27.0
• Node Version: 16
• npm Version: 6
• Operating System: windows

What parser (default, @babel/eslint-parser, @typescript-eslint/parser, etc.) are you using?

default(espree)

Please show your full configuration:

Configuration

// I don't think this is useful

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

I want check a property is Object’s own property,

Object.prototype.hasOwnProperty(property);

no-prototype-builtins reports an error.

Object.prototype.hasOwnProperty.call(Object.prototype, property);

no-useless-call reports an error.

What did you expect to happen?

no-useless-call rule should ignore Object.prototype.hasOwnProperty.call(Object.prototype, ...)

What actually happened? Please copy-paste the actual, raw output from ESLint.

N/A

Steps to reproduce this issue:

N/A

Are you willing to submit a pull request to fix this bug?

No

[nzakas]

Yeah, I also agree that this is more of an edge case and I can’t see a generic way to solve the conflict that doesn’t cause other problems. When there are as many core rules as ESLint has, it just gets difficult to make them all play together in every configuration.

[fisker]

I updated expect to

no-useless-call rule should ignore Object.prototype.hasOwnProperty.call(Object.prototype, ...)