Closed mgutz closed 3 years ago
Both of these are actually available but not shown by the built-in diagnostics handlers. I recommend trouble.nvim, which will show you both the source and the rule ID (and generally provide a more VS Code-like experience with diagnostics).
vscode shows the source of the linting issue (eslint or typescript) and the code for the failed rule. It's hard to disable errors or find online solution without this info. Is that possible with this plugin?