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

Add WebSocket support and launcher #108

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

haydenbaker
Copy link

@haydenbaker haydenbaker commented May 23, 2023

Description of changes:

  • Add websocket support for LSP, such that using the LSP over websockets is possible
  • Add README snippets about launch options

Testing:

  • Launch WSS via ./gradlew run --args="3000 --ws", confirm a websocket client can connect and communicate with it
  • Launch stdin/stdout via ./gradlew run --args="0", confirm no behavior change
  • Bump version, Publish to maven local, update vscode extension version, confirm no behavior change

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@haydenbaker haydenbaker requested a review from a team as a code owner May 23, 2023 16:03
@haydenbaker haydenbaker force-pushed the websocket-support branch 2 times, most recently from 935b2ff to ee271aa Compare May 23, 2023 17:43
try {
String port = args[0];
Optional<Exception> launchFailure;
Copy link
Contributor

Choose a reason for hiding this comment

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

Declaration can go down with the assignment


#### WebSockets

Run `./gradlew run --args="3000 --ws"`
Copy link
Member

Choose a reason for hiding this comment

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

Can you put --ws in front? I would assume here that 3000 is a positional argument that comes after named arguments, and those are usually last.

Copy link
Contributor

Choose a reason for hiding this comment

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

perhaps it's also worth considering the deprecation of port as a positional argument and making it a --port option? For some time the server could support both styles, but eventually the positional way would be dropped.

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.

5 participants