-
Notifications
You must be signed in to change notification settings - Fork 301
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
Create a language server proof-of-concept #5176
Labels
development-issue
Issues encountered while developing RD, not in RD itself
Comments
mansellan
added
the
development-issue
Issues encountered while developing RD, not in RD itself
label
Oct 3, 2019
Just interested if there's been any movement on this prototype? |
Not completed-completed, but LSP (via OmniSharp) is going to work over named pipes in RD3 - still WIP, but the concept has been proven. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#5121 discusses the possibility of splitting Rubberduck into a client/server architecture, to solve various performance and scaling constraints, and proposes Language Server Protocol as a possible means of implementation.
Before we invest any further in this idea, we need a proof-of-concept to explore the technology, determine whether it is suitable for our use, and identify any shortcomings.
Initially, the following approach will be attempted:
The text was updated successfully, but these errors were encountered: