-
Notifications
You must be signed in to change notification settings - Fork 110
LspRouter update, update Supports<>
#36
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
LspRouter update, update Supports<>
#36
Conversation
@tintoy going to push this as |
Cheers! Will give it a go in an hour or so |
What's the expected behaviour for requests / notifications where multiple handlers for the same method are registered? |
Ah, needs a logger factory now; will add one. |
Add Microsoft.Extensions.Logging and hook it up to Serilog. OmniSharp/csharp-language-server-protocol#36
Yep! Works fine, cheers :) |
Oops, spoke too soon:
As shown here: |
Looks like the overload of |
I didn't get to this last night... fixing shortly. |
Two things:
ITextDocumentSyncHandler
previously this would pick the first one, which was only right if the one you wanted was first. No other handlers would.ITextDocumentSyncHandler.GetTextDocumentAttributes
can return null, previously this was assumed to be not null.LspRequestRouter
to ensure it's working as intended (I hope, 😱)ClientCapabilities
is incompatible with other LSP implementations. #35 using the hacky feelingShouldSerializeX
inNewtonsoft.Json
. There is be a better way I'm sure, but these methods will be hidden from intellisense for consumers.