no-console rule should document how to enforce calls only via no-restricted-syntax

What rule do you want to change?

The no-console rule.

Does this change cause the rule to produce more or fewer warnings?

Fewer warnings.

How will the change be implemented? (New option, new default behavior, etc.)?

I’m thinking it would be default behavior, but could also be configured.

Please provide some example code that this change will affect:

In our development and test environments we have this snippet to suss out warnings in our Javascript:

console.error = function (message) {
  throw new Error(message);
};

What does the rule currently do for this code?

The rule currently reports Unexpected console statement.

What will the rule do after it’s changed?

It will not report any errors for assignment to console.

[platinumazure]

I don’t think it’s worth changing the rule for this use case. Instead, you can use a disable comment to ignore the rule in this location.

Here are two ways you can do this:

// eslint-disable-next-line no-console
console.error = function (message) {
  throw new Error(message);
};

// Or (equivalent)

console.error = function (message) {  // eslint-disable-line no-console
  throw new Error(message);
};

Of course, you could also just use the no-console rule to statically detect all of your console.error invocations and replace them with error throwing, as needed. 😄

[platinumazure]

Editing the title of this issue to reflect the TSC decision.