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

Support for Language Server Protocol - part 2 #2109

Closed
gazarenkov opened this issue Aug 12, 2016 · 1 comment
Closed

Support for Language Server Protocol - part 2 #2109

gazarenkov opened this issue Aug 12, 2016 · 1 comment

Comments

@gazarenkov
Copy link
Contributor

@gazarenkov gazarenkov commented Aug 12, 2016

This is the second part of LS protocol implementation:

  • Language Server Protocol: ShowMessage Notification feature #1793
  • Language Server Protocol: ShowMessage Request feature #1794
  • Language Server Protocol: Telemetry Notification #1796
  • Language Server Protocol: DidChangeWatchedFiles Notification #1799
  • Language Server Protocol: Document Highlights #1802
  • Language Server Protocol: Push notification to client on new language server #1427
  • Language Server Protocol: Ensure order of Events #1426
  • Language Server Protocol: Rename feature #1806 (depends on #5955)
@TylerJewell
Copy link
Contributor

@TylerJewell TylerJewell commented Aug 20, 2016

@gazarenkov - before we implement this second phase, we need to consider the following usability improvements:

  1. Softening some of the treatment of the phase 1 elements so that they have a more modern design to them vs. the heavy black lines.
  2. End user acceptance / rejection / installation / uninstallation of LS agents from within the IDE. LS will have licenses that require acceptance of the end user before they are installed into the ws. We should enable this capability in the UD & probably the IDE at the same time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.