Godot: Less aggressive error highlighting ?

[DriNeo]

Godot main devs works currently on the editor and GDscript usability, maybe it's the time to submit my proposal.

I found the error highlighting during text edition a bit disturbing.
I suggest to highlight only the number line column, this column is always visible. I painted this zone in the following image.

[neikeq]

I don't know... this can be confused with a breakpoint.

[akien-mga]

I think it's fine that error highlighting is aggressive, as errors need to be fix right away since they prevent compilation and code completion.

On the other hand it's true that when the error is on the line you are still in the middle of writing, it's a bit too much. Suggestions welcome on how to improve this use case specifically without changing general error display in another section of the code. :)

[bojidar-bg]

Well, maybe we can highlight the line in some color inbetween the "current line" color and the "error line" color?

[DriNeo]

@akien-mga: I'm totally agree with the dynamic highlighting system, it's very useful.

To make this less disturbing, an alternative might be to just remove the highlighting if the cursor is moved or if anything is entered in the failed line. The highlighting will come back after one second of standby.

[BBric]

A larger lines numbers column for let the place to small icons, and in this case for example a classical exclamation mark in a red circle.

[ghost]

This is how it looks in 3.0

Still an issue. Highlight of the text in that area is almost indistinguishable.

[volzhs]

I got this result with selection color alpha = 1.0 (custom color though)
it seems to be indistinguishable with overlapping 3 colors with alpha.

[nikhilCad]

I like the way vscode does it. Not aggressive, but still catches attention.

[Calinou]

@nikhilCad I did something similar in #35962, though I still kept a subtle whole-line error highlighting as it makes it much easier to spot the error while you're in a hurry.

[DriNeo]

IMO the Calinou PR may fix this issue.

[Calinou]

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.

The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.

If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!