Add option for notification / code highlight on parsing errors
See original GitHub issueIs your feature request related to a problem? Please describe. Lets assume I don’t run a linter because I’m working on an external code base, I run prettier and nothing happens. The small warning icon often goes under the radar when something goes wrong.
Describe the solution you’d like Two options:
- Highlight the offending code in the editor
- Show a notification with a reduced error message, maybe something like this:
Prettier: Error formatting document
07 | ,typo
> 08 | const fn1 = (...) => {
| ^
09 |
Additional context This should of course be an option configurable via settings. I feel like I can’t be the only one overseeing the small warning from time to time.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
How can I solve the issue where VS code highlight for errors ...
am using php I have the common extensions added but i just cant remove this annoying bug that highlights for errors on lines...
Read more >Syntax Highlighting and Error Highlighting - consulo.dev
TIP To force re-highlighting, use DaemonCodeAnalyzer.restart() . The syntax and error highlighting are performed on multiple levels: Lexer, Parser, and ( ...
Read more >Syntax Highlighting - GitLab Docs
GitLab provides syntax highlighting on all files through Highlight.js and the Rouge Ruby gem. It attempts to guess what language to use based...
Read more >Syntax and Error Highlighting | IntelliJ Platform Plugin SDK
The syntax highlighter returns the TextAttributesKey instances for each token type, which needs special highlighting. For highlighting lexer errors, ...
Read more >February 2022 (version 1.65) - Visual Studio Code
For that reason, we are adding several UI options for everyone to try ... This includes parsing errors, as well as invalid redeclarations...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, I haven’t seen that. Good to know!
So there is a sign but it has to be seen by the user. 😛
But the failure notification also would be good so I think you should at least consider it.
Well, maybe there are other extensions available but the option to turn on notifying of parser failure would be welcomed. At least by me as the user. Because at the moment (as I wrote in #1419) there is no sign that something went wrong.