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

Revert PR #7579 ("Using LSP's ErrorProvider & another attempt at CompletionCollector") #7650

Merged
merged 2 commits into from
Sep 2, 2024

Conversation

matthiasblaesing
Copy link
Contributor

Closes: #7647

…ditional resolved.getDocumentation() can be null"

This reverts commit c7eda4f.
@matthiasblaesing matthiasblaesing added LSP [ci] enable Language Server Protocol tests VSCode Extension [ci] enable VSCode Extension tests ci:all-tests [ci] enable all tests ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) labels Aug 8, 2024
@matthiasblaesing matthiasblaesing added this to the NB23 milestone Aug 8, 2024
@jtulach
Copy link
Contributor

jtulach commented Aug 9, 2024

If possible, please give me time over the weekend to investigate a different fix than removal of the changes.

@matthiasblaesing
Copy link
Contributor Author

@jtulach from my POV no problem. This PR is the safety net.

@jtulach
Copy link
Contributor

jtulach commented Aug 11, 2024

If

gets in, then this revert will no longer be needed.

Copy link
Contributor

@jtulach jtulach left a 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.

@matthiasblaesing
Copy link
Contributor Author

Lets keep the discussion in #7659.

@ebarboni
Copy link
Contributor

as #7659 is closed maybe continuing discussion here ?
(sorry for delay but not in my place this time) Do not over rely on me.

Copy link
Member

@mbien mbien left a 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)

@lahodaj
Copy link
Contributor

lahodaj commented Sep 2, 2024

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.

@jtulach jtulach dismissed their stale review September 2, 2024 11:29

While I don't agree with full revert of my changes, I certainly don't want to block decisions of the majority

@MartinBalin MartinBalin merged commit 4fd016e into apache:delivery Sep 2, 2024
40 checks passed
@mbien mbien linked an issue Sep 3, 2024 that may be closed by this pull request
@matthiasblaesing matthiasblaesing deleted the issue-7647 branch September 17, 2024 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci:all-tests [ci] enable all tests ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) LSP [ci] enable Language Server Protocol tests VSCode Extension [ci] enable VSCode Extension tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Duplicate text in hint tooltip
7 participants