Skip to content

Switch to upstream positionEncoding #13484

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

Merged
merged 2 commits into from
Oct 26, 2022
Merged

Conversation

lnicola
Copy link
Member

@lnicola lnicola commented Oct 25, 2022

Closes #13481

This drops support for the custom extension, but that's probably fine.

Draft because it's not tested yet.

@@ -23,7 +23,7 @@ crossbeam-channel = "0.5.5"
dissimilar = "1.0.4"
itertools = "0.10.5"
scip = "0.1.1"
lsp-types = { version = "0.93.1", features = ["proposed"] }
lsp-types = { version = "0.93.2", features = ["proposed"] }
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
lsp-types = { version = "0.93.2", features = ["proposed"] }
lsp-types = { version = "=0.93.2", features = ["proposed"] }

We might wanna pin our lsp-types version to prevent breakages like these in the future

Copy link
Member Author

@lnicola lnicola Oct 25, 2022

Choose a reason for hiding this comment

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

This was lsp-types breaking semver in a minor release, but sure, it can't hurt. I just hope we don't end up doing this for every dependency.

Or we could do ..Default::default().

Copy link
Member

Choose a reason for hiding this comment

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

Oh for some reason I thought they were breaking by keeping versions numbers in sync, but thats not the case. Nevermind then, that's just unfortunate i guess

Copy link
Member Author

Choose a reason for hiding this comment

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

It's fine to pin it, I think it's not the first time something like this happens. But if rather not use default() so that we know when something new gets added there.

Copy link
Member

Choose a reason for hiding this comment

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

gluon-lang/lsp-types#248 (comment) so ye, pinning is the right choice for us here

@lnicola lnicola marked this pull request as ready for review October 26, 2022 14:34
@lnicola
Copy link
Member Author

lnicola commented Oct 26, 2022

@bors r+

@lnicola
Copy link
Member Author

lnicola commented Oct 26, 2022

@bors ping

@bors
Copy link
Contributor

bors commented Oct 26, 2022

😪 I'm awake I'm awake

@lnicola
Copy link
Member Author

lnicola commented Oct 26, 2022

@bors r+

@bors
Copy link
Contributor

bors commented Oct 26, 2022

📌 Commit e93a2bf has been approved by lnicola

It is now in the queue for this repository.

@bors
Copy link
Contributor

bors commented Oct 26, 2022

⌛ Testing commit e93a2bf with merge 0340b51...

@bors
Copy link
Contributor

bors commented Oct 26, 2022

☀️ Test successful - checks-actions
Approved by: lnicola
Pushing 0340b51 to master...

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.

missing field position_encoding in initializer of ServerCapabilities
3 participants