Coder Social home page Coder Social logo

languageserverprotocol's People

Contributors

atsushieno avatar matarillo avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

languageserverprotocol's Issues

Parameter information not displaying correctly in VS Code...

I am creating function signature help for a language that I'm enabling in VS Code. I am having an issue where only one of the function parameters displays in VS Code. Is this known behavior or am I doing something wrong?

SignatureHelp test = new SignatureHelp();

var sig = new SignatureInformation();
sig.label = "shuffle";
sig.documentation = "shuffle(float v, int i)";

sig.parameters = new []
{
	new ParameterInformation
	{
		label = "float",
		documentation = "Float register."
	},
	new ParameterInformation
	{
		label = "int",
		documentation = "Bits to shuffle."
	}
};

test.signatures = new SignatureInformation[1];
test.signatures[0] = sig;

return Result<SignatureHelp, ResponseError>.Success(test);

lsp_signature

Cheers,

Pete

LSP process does not terminate and spins with full CPU usage

I'm trying to support LSP using your implementation and some PoC code working (https://twitter.com/atsushi_eno/status/1021226599172038656).

Though it is not really ready to let others try, because the LSP process somehow does not terminate. Even worse, after vscode itself quits it spins like it were using SpinWait. It seems to happen to your LSP example project too. It does quit when I quit vscode for the language client project though (i.e. closing "extension host" causes spinwait. Closing vscode for LS client folder stops it).

screenshot from 2018-07-23 12-20-54

Is there any way to explicitly shut down the LSP process by any LS requests like Exit()? It does not seem to work either.

Add option to add handlers manually

Thank you for the nice lightweight implementation :-)

I'd suggest making ConnectionHandlerProvider public or otherwise add a way to invoke AddHandlers manually. Currently one has to derive from ServiceConnection and override all methods in the same class. I would be more convenient if one could add handlers implemented in different classes.

This part:

protected ServiceConnection(Stream input, Stream output)
...
       var provider = new ConnectionHandlerProvider();
       provider.AddHandlers(Handlers, this.GetType());
}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.