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

fix: restore error handling for server #1306 #1425

Merged
merged 1 commit into from
Mar 14, 2020

Conversation

acao
Copy link
Member

@acao acao commented Mar 14, 2020

seems that vscode-languageserver deprecated writing to stderr by default

also removing direct calls to process in the underlying language service so that it's compatible with non-node runtimes. trapping the exceptions in startServer should handle exceptions, but we should make sure that the editor events that we don't return from in those cases continue firing as normal?

CC: @divyenduz , @zth

seems that vscode-languageserver deprecated writing to stderr by default
@acao acao added this to In progress in 3. Complete LSP Features via automation Mar 14, 2020
@acao acao added lsp-server graphql-language-service-server lsp cli labels Mar 14, 2020
@acao acao merged commit c12d975 into master Mar 14, 2020
3. Complete LSP Features automation moved this from In progress to Done Mar 14, 2020
@acao acao deleted the fix/1306-error-handling-lsp branch March 14, 2020 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lsp cli lsp-server graphql-language-service-server
Projects
Development

Successfully merging this pull request may close these issues.

None yet

1 participant