Rule Change: no-console could be fixable

[edi9999]

What rule do you want to change?

no-console

What change to do you want to make?

Implement autofix

How do you think the change should be implemented?

A new option

Example code

I debug a lot with console.log, and have to remove them all afterwards.

Some console.log I write are multiline, like this :

console.log(
	JSON.stringify({
		msg: "inspect-sectObj",
		inspect: util.inspect(sectObj, { showHidden: true, depth: 2 }),
	})
);

What does the rule currently do for this code?

It will simply report the error

What will the rule do after it's changed?

It could fix the error, removing the console.log alltogether

Participation

• I am willing to submit a pull request to implement this change.

Additional comments

I know this has not been implemented on purpose, probably people don't want all their console.logs dropped by eslint by default, I would also like to be able to make this rule fix only on certain conditions.

[edi9999]

For the moment I will continue removing my console.log manually, it is just (a bit) annoying when you do it twice a day for 5 minutes and you know you will do so in the future 5-10 years)

[mdjermanovic]

Hi @edi9999, thanks for the proposal!

We can't implement this as autofix, because autofixes should never change the runtime behavior of code. This is the policy for core rules and general advice for plugins (though, you can find an equivalent but autofixable no-console rule in eslint-plugin-autofix).

We could only consider implementing this in the core no-console rule as suggestions, if that seems useful to you?

[edi9999]

Interesting, how can I access the suggestions ?

Is there a way to access them from the command line ? If yes, I would be interested in first having an example output in the command line, then I could write the code for the suggestion of the console.log rule.

[mdjermanovic]

Suggestions can be applied through editors that support this feature.

For example, in VS Code:

(Remove the `\`... and Replace the `\`... are two suggestions; when user selects a suggestion, editor applies the fix).

There's no built-in support for applying suggestions from the command line.

[Dimava]

Removing console with autofix should be a standalone plugin
And it already exists as https://www.npmjs.com/package/eslint-plugin-fulldo-remove-console
(I would prefer an on-github alternative with more options, this one can only remove console.logs with no rule config)

[edi9999]

So you mean you wouldn't be open to add the "suggestion" to console.logs ?

I'm using neovim as my editor so I'm not sure whether I can use suggestions at all, that's why I asked whether I could do something from the command line.

[mdjermanovic]

The ESLint team would be open to evaluating adding suggestions to the no-console rule.

I'm using neovim as my editor so I'm not sure whether I can use suggestions at all, that's why I asked whether I could do something from the command line.

Not sure either, but you could try with a code example where suggestions are expected to appear:

/* eslint no-useless-escape: "error" */

"\a";

The expected suggestions are as in this demo.

[nzakas]

Marking as accepted.