guard-for-in doesn't recognize that Object.entries() is returning an array for for...in loop

• ESLint Version: 4.14.0
• Node Version: v8.0.0
• npm Version: 5.6.0 What parser (default, Babel-ESLint, etc.) are you using? babel-eslint 8.1.2

Configuration

```js { "extends": "airbnb-base", "parser": "babel-eslint", "env": { "jest": true }, "rules": { "arrow-parens": "off", "no-throw-literal": "error", "no-void": "off", "import/prefer-default-export": "off", "valid-jsdoc": "error", "no-unused-expressions": [ "error", { "allowShortCircuit": true, "allowTernary": true } ] } } ```

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

for (const file in Object.entries(newMockFiles)) {
 ...
}

Command ran:

eslint src

What did you expect to happen? No linting error. The linter should recognize that the for...in is iterating over an array.

What actually happened? Please include the actual, raw output from ESLint. error The body of a for-in should be wrapped in an if statement to filter unwanted properties from the prototype guard-for-in

[platinumazure]

I see an error when I have something in the body, whether working with an array-returning function or an array literal. Demo here.

I don’t think the rule was designed to care about the type of the iterated object. So I’m having a hard time seeing this as a bug.

[not-an-aardvark]

Closing because this is working as intended.