Vscode-eslint: rulename no longer shows

[wmertens]

In some recent update, not sure of eslint or this plugin, the eslint rule name stopped showing.

This means I can't easily look it up or disable it.

Can this be reinstated? Preferably, the rulename is the first part of the error message, so it's easy to copy and paste.

[GStipick]

I am also having the same problem. It appears that work is being done to fix this though.

Reference:
https://github.com/Microsoft/vscode-eslint/pull/562

[Friksel]

Same problem here, perhaps something changed in the latest VS Code upgrade? Using the latest VS Code (1.28.2).

Like @wmertens I also use this to quickly copy and paste the rule-id to a // eslint-disable-line. Without the rule in the message it's not quick and easy to find the rulenames for the messages.

[dbaeumer]

Two things: the missung rule name is caused by a bug in VS Code which is already fixed in Insider and will be available in the next stable version appearing soon.

Due to a PR I got from @loune the quick fix now contains actions to disable a rule. No need to copy paste anymore.

[Friksel]

Thanks for the info @dbaeumer and great to have an action for it! I also just found out that the rule-names are still visible in the 'problems' tab, so there's no need to search for the eslint-names anymore.

[Friksel]

@dbaeumer When using the new 'Suppress ... for this line' action we don't get the suppression on the same line, but as a // eslint-disable-next-line instead of a // eslint-disable-line. I normally put these on the same line as the suppressed line for better readability and less disturbing code flow, but this seems to be impossible with this workflow. Would it be possible to make the 'Suppress .. for this line' insert the suppress-line on the same line as the code (eslint-disable-line) and perhaps move the current behaviour to an additional action to add it to the next line (eslint-disable-next-line)? Thanks!

[dbaeumer]

@Friksel can you please open a separate issue for this?

[Friksel]

@dbaeumer Hereby: https://github.com/Microsoft/vscode-eslint/issues/573