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
VS Code by default turns auto-detectable file path indicators in terminals into cmd/ctrl-clickable links to open the file in the editor. If there's a line:col indicator or similar it'll pick that up too. The detection by default picks up ESLint's default stylish reporter.
Typically, the whole ESLint message turns into a clickable link:
Unfortunately, that means the GitHub link to the module's .md file isn't itself clickable. You have to manually select it. Irksome!
You can get around this by putting a \n in the report message, like:
Personally, I think this is an issue for VS Code that it should respect the URL without \n trickery. But I figured I'd raise here and see what you think 🙂. Someone should probably search for / file an issue on VS Code.
The text was updated successfully, but these errors were encountered:
VS Code by default turns auto-detectable file path indicators in terminals into cmd/ctrl-clickable links to open the file in the editor. If there's a
line:col
indicator or similar it'll pick that up too. The detection by default picks up ESLint's defaultstylish
reporter.Typically, the whole ESLint message turns into a clickable link:
Unfortunately, that means the GitHub link to the module's
.md
file isn't itself clickable. You have to manually select it. Irksome!You can get around this by putting a
\n
in the report message, like:Personally, I think this is an issue for VS Code that it should respect the URL without
\n
trickery. But I figured I'd raise here and see what you think 🙂. Someone should probably search for / file an issue on VS Code.The text was updated successfully, but these errors were encountered: