Peter Weinberger d238219cc2 internal/lsp: client/registerCapapbility is a request, not a notification ... Although they have null responses, client/[un]registerCapability messages are RPCs from golps to the editor, not notifications. (This bug had unknown impact.) Change-Id: I3be2eb30b46f937b8ec29d1668f682b797d84be9 Reviewed-on: https://go-review.googlesource.com/c/tools/+/179157 Reviewed-by: Ian Cottrell <iancottrell@google.com> Run-TryBot: Peter Weinberger <pjw@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>		2019-05-28 15:12:38 +00:00
..
typescript	tools/internal/lsp/protocol: generate LSP protocol types from source	2019-03-12 15:15:45 +00:00
doc.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00
enums.go	internal/lsp: switch completion item tests to using the enum strings	2019-04-17 17:57:43 +00:00
log.go	internal/lsp: add the ability to log back to the client	2019-04-01 16:22:08 +00:00
protocol.go	internal/lsp: add the ability to log back to the client	2019-04-01 16:22:08 +00:00
span.go	internal/lsp: update column mapper with content on incremental changes	2019-05-20 19:04:59 +00:00
tsclient.go	internal/lsp: client/registerCapapbility is a request, not a notification	2019-05-28 15:12:38 +00:00
tsprotocol.go	internal/lsp: remove SelectionRange and textDocument/selectionRange	2019-05-24 12:55:31 +00:00
tsserver.go	internal/lsp: remove SelectionRange and textDocument/selectionRange	2019-05-24 12:55:31 +00:00