-
Notifications
You must be signed in to change notification settings - Fork 874
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
Revert PR #7579 ("Using LSP's ErrorProvider & another attempt at CompletionCollector") #7650
Conversation
If possible, please give me time over the weekend to investigate a different fix than removal of the changes. |
@jtulach from my POV no problem. This PR is the safety net. |
If gets in, then this revert will no longer be needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problems reported by
are only related to HintsCollector.setError. However the #7579 PR introduces two things:
HintsCollector.setError
- another attempt at
CompletionCollector
there is no point in reverting all. If none of other solutions works (like #7659), then we need to revert only the HintsCollector.setError
part and keep the rest. I can prepare such a revert PR during the next 24 h.
Lets keep the discussion in #7659. |
as #7659 is closed maybe continuing discussion here ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for NB 23 revert (#7659 (comment) for reasons)
FWIW, while I am not particularly happy the bridge between LSP API and client will cease to work for NB 23, I think this should be merged, and we should see if we can achieve the same end goal using a more scalable approach. |
While I don't agree with full revert of my changes, I certainly don't want to block decisions of the majority
Closes: #7647