You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.
This is not a bug, a lot of people have been dropping atom for VS code, and linting is a huge part of that. The one gripe is that errors aren't as easily visible, if you don't have the problems tab opened. And the tiny red line isn't enough.
This has a great example SCSS Lint Version where it highlights the offending area in red.
The second is, in ATOM, you can click on the rule and it would take you to documentation, is that a future enhancement?
Otherwise no other major issues.
The text was updated successfully, but these errors were encountered:
You can follow this issue for updates regarding the styling of diagnostic errors. I don't think that there is anything that I can do to control these styles. The extension that you mention doesn't seem to use the same APIs as those used by the tslint or eslint extensions (as well as this one).
Regarding the 2nd issue, if I'm not mistaken, this also requires support in VS Code itself. See this issue for more information.
This is not a bug, a lot of people have been dropping atom for VS code, and linting is a huge part of that. The one gripe is that errors aren't as easily visible, if you don't have the problems tab opened. And the tiny red line isn't enough.
This has a great example SCSS Lint Version where it highlights the offending area in red.
The second is, in ATOM, you can click on the rule and it would take you to documentation, is that a future enhancement?
Otherwise no other major issues.
The text was updated successfully, but these errors were encountered: