Add support for textDocument/inlayHint #702
Conversation
The following are added manually to the generated code: * inlayHint/resolve * textDocument/inlayHint Generating this code is currently not possible since the upstream gopls generator was migrated from Typescript to Go just before the 3.17 LSP release. Using the new generator requires some more work and adaptions on our side.
|
Ping @5nord This is a 3.17 LSP feature. I manually copied the new structures from gopls. They no longer use the typescript-based codegen scripts. For now this seems to work. I suggest tackling the proper (automated) protocol upgrade separately in a new PR. |
|
This is how it looks in neovim (nightly) with also semantic tokens enabled. Neovim does not work well with dynamic capabilities yet, I needed to tweak the plugin a bit. I can share my config if you want to try this. I also tried vscode but it looks like the client does not send the inlayHint capability - perhaps the extension needs to be updated.
|
|
I will review your PR in a few days, when I am back from child leave. Is that okay with you? |
That is perfectly fine. I am aware you're on leave, that's why I reached out on github. Thanks! |
This PR adds initial support for inlay hints (only textDocument/inlayHint method) for function and template calls.
Fixes #701.