Display "ESLint" and the triggered rule within the tooltip about vscode-eslint HOT 6 CLOSED

Now that I've started to work with TSLint I'm starting to feel the same, that is I'd like to see whether are warning comes from TypeScript or TSLint.

@dbaeumer I suggest we come up with a guideline and then apply it across all the linters.

My preference would be to show the linter/source at the end of the message, i.e.,

You have done something stupid (stupid-syntax-rule) [ESLint]

The message is the 'main' thing and it should come first before the linter which is secondary information.

from vscode-eslint.

@egamma - I agree.

from vscode-eslint.

I think we should not mangle this (from an API perspective) into the message. Instead we should enhance the Diagnostic API with a source field and allow linters to fill in that field. This would allow for proper filtering and grouping in the UI side. See microsoft/vscode#1010 for the discussion on the VS Code side.

from vscode-eslint.

I was only taking about the rendering.. Fully agree, that this should not be done with string concatenation, but an API.

from vscode-eslint.

This got addressed a long time ago.

from vscode-eslint.

Got fixed a long time ago.

from vscode-eslint.