Skip to content

Conversation

@travkin79
Copy link
Contributor

Adapt LSP4E to LSP4J API changes as suggested by @jonahgraham. Other PRs requiring LSP4J vers. 1.0.0 like PR #1149 will base upon changes from this PR.

@sebthom
Copy link
Member

sebthom commented Nov 25, 2025

We should hold merging this back until LSP4J 1.0 is actually released otherwise we are blocked from cutting LSP4E releases ourselves from now on.

@travkin79
Copy link
Contributor Author

Hi @sebthom,

We should hold merging this back until LSP4J 1.0 is actually released...

I expected that. Would you prefer to change this PR's status to draft?

@sebthom
Copy link
Member

sebthom commented Nov 25, 2025

I think that is appropriate for now.

@travkin79 travkin79 marked this pull request as draft November 25, 2025 15:29
Copy link
Contributor

@jonahgraham jonahgraham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM - I have done code inspection, but not run it up in LSP4E.

For the sake of simplicity, for now, we only use the left argument in
Either tuples, i.e. the types that we used in earlier versions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants