no-console warns on assignment

[sachinraja]

Tell us about your environment

• ESLint Version: v7.30.0
• Node Version: v16.4.0
• npm Version: v7.18.1
• Operating System: linux 5.8.0-58-generic

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

Please show your full configuration:

Configuration

module.exports = {
  parserOptions: {
      ecmaVersion: 6
  },
  rules: {
    "no-console": "warn",
  },
}

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

console.log = jest.fn()

npx eslint .

What did you expect to happen?
The no-console rule should detect that this is an assignment and not a call. In the rule details it says "This rule disallows calls to methods of the console object."

What actually happened? Please copy-paste the actual, raw output from ESLint.
warning Unexpected console statement no-console

Steps to reproduce this issue:

1. in your eslint configuration add no-console: 'warn' to your rules.
2. in your code, set console.log = null

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

[mdjermanovic]

Hi @sachinraja, thanks for the issue!

console.log = jest.fn()

This was already discussed in #7806, and it was eventually decided that this behavior shouldn't be changed.

If you want to disallow only method calls, you can use the no-restricted-syntax rule, as described in When Not To Use It section of no-console docs ("Another case where you might not use this rule is if you want to enforce console calls and not console overwrites...").

In the rule details it says "This rule disallows calls to methods of the console object."

You're right, this sounds misleading. I'm marking this issue as an accepted documentation change.