Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-standard Error Highlighting Declaring New Functions #1023

Closed
CanIGetaPR opened this issue Sep 26, 2020 · 4 comments
Closed

Non-standard Error Highlighting Declaring New Functions #1023

CanIGetaPR opened this issue Sep 26, 2020 · 4 comments
Labels
Change Request Feature changes that are neither bugs nor enhancements.

Comments

@CanIGetaPR
Copy link
Collaborator

It's a bit distracting when I start writing a function and it highlights all the code below that instead of just underlining at the source line. I haven't ever seen this before in IntelliJ IDEs. The highlighted text has a pop-up tip that reads "un-parseable code"

image

Here's how they do it in Java, just a little underline where something more is expected:

image

@EricBishton
Copy link
Member

The primarily motivation for the feature is to indicate why activity and changes that occur in a region don't have proper functionality: Things like Go To Definition (F4), and Refactorings, and Parameter Affordance (Ctrl+P). Also note that there is a tiny red line at the point at which the parser detects the error. The highlighting follows the red line, usually immediately, but sometimes later, as in the first image posted above.

That said, if it is annoying to you (and I understand that it is for some people), it is easily disabled: Use the settings dialog to edit the Haxe color scheme (File->Settings: Editor > Color Scheme > Haxe), select the "Unparseable Data" line, and deselect the check boxes.

image

@EricBishton EricBishton added the Change Request Feature changes that are neither bugs nor enhancements. label Sep 26, 2020
@CanIGetaPR
Copy link
Collaborator Author

Should probably fix #1024 , and that will fix this.

@CanIGetaPR
Copy link
Collaborator Author

You know what it's like a race now, if I type out the declaration quickly enough the highlighting doesn't happen. It only happens when I stutter. ;)

@EricBishton
Copy link
Member

It only happens when I stutter. ;)

😄

One thing is for sure: It lets you know what the parser is having issues with. Most folks wonder what this is at first, and once they figure it out, quickly get used to it and/or change the colors so that it's not as distracting to them. (And the colors I picked as default aren't distracting to me.) I don't know of anybody who has totally disabled the feature once they understood it, but I'm sure there are some who have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Change Request Feature changes that are neither bugs nor enhancements.
Projects
None yet
Development

No branches or pull requests

2 participants