Skip to content

Add support for setting up language servers to use websockets #620

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

MangoIV
Copy link
Contributor

@MangoIV MangoIV commented Aug 8, 2025

Allow the user to set up an lsp server that talks to the user using the websocket protocol instead of standard IO and do enough refactoring to make the setup with websockets possible

@MangoIV MangoIV changed the title Add support for setting up language servers using to use websockets Add support for setting up language servers to use websockets Aug 9, 2025
@MangoIV
Copy link
Contributor Author

MangoIV commented Aug 9, 2025

I have tried to make as few breaking changes as possible (I don't think there are any) except that I changed from BS.ByteString and BSL.ByteString (which are not visible in the haddock) to BS.StrictByteString and BSL.LazyByteString (which are visible in the haddock) Unfortunately these are very recent additions, so let me know if I should revert them for the sake of better backwards compatibility with older bytestring versions.

Allow the user to set up an lsp server that talks to the user using
the websocket protocol instead of standard IO and do enough refactoring
to make the setup with websockets possible
@MangoIV MangoIV force-pushed the mangoiv/websocket branch from 679c8f1 to e07c7e3 Compare August 9, 2025 10:30
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.

1 participant