-
Notifications
You must be signed in to change notification settings - Fork 240
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
Fix error highlighting in IDE. #715
Conversation
Hey @benfry! It looks like some ambiguity in |
CC @SableRaf |
Doing one bit of cleanup this morning but we should prioritize this |
Start refactor of #715 to specific optionals.
Cool did the clean up! Ready for review... I think it's probably best to have client code indicate which type of start offset it wants when interacting with a problem. I've tested the PDE... checking language server. |
…ng4 into differentiate-offset
Yay! Confirmed language server working. :D |
I know we don't have an imminent release but this is is getting in the way of a GSoC project. To make sure he can still finish on time / pass, I'm going to merge this to main but I won't make a release. Without this sorted, the error message rewriting isn't visible to the user. |
Error highlighting is a bit broken (see #714).
Root cause: Depending on how the
Problem
is made, the error may be given relative to start of line or start of tab. Changed method names to indicate to users ofProblem
s which one they are working with.I think this may have been introduced in the language server support effort as
Problems
may be made without Editor available. The behavior in #714 appears to have started then but there was a delay before it showed up in production given how releases were done.Resolution: I clarified the interface and gave client code ability to determine if they want / need a
Problem
to be placed relative to start of line or start of tab where each are more convenient in different contexts.