question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add option for notification / code highlight on parsing errors

See original GitHub issue

Is 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:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
Nircekcommented, Jun 17, 2020

Thanks, I haven’t seen that. Good to know!

Because at the moment (as I wrote in #1419) there is no sign that something went wrong.

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.

1reaction
Nircekcommented, Jun 8, 2020

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.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found