Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`hasOwnProperty` is not detected with `no-undef`

See original GitHub issue

Tell us about your environment

ESLint Version: 5.3.0
Node Version: 11.0.0-pre
npm Version: 6.2.0

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

default

Please show your full configuration:

no-undef: error

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

Demo

What did you expect to happen?

An error should be reported.

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

Nothing is reported. It is specific to this function name.

Issue Analytics

State:
Created 5 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

not-an-aardvarkcommented, Aug 12, 2018

I think this is working as intended because the global object typically has Object.prototype on its prototype chain, so referencing a property like hasOwnProperty will read that value. I’ve seen hasOwnProperty.call(foo, bar) used as an alternative to Object.prototype.hasOwnProperty.call(foo, bar).

0reactions

BridgeARcommented, Aug 12, 2018

Oh, you are right. Thanks for pointing this out! I just ran into an issue with it because I used uncurryThis to prevent tampering of the globals… I guess this is a special case without an ideal solution.