You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In VSCode if you set the setting swift.sourcekit-lsp.server.trace to verbose you can see all the communication between the VSCode LSP client and SourceKit-LSP in the SourceKit-LSP output pane. Useful for debugging requests. Search for InlayHint and you should see the requests.
@adam-fowler thank you for the advice! I checked it in VSC and it turned out that my request is the same. I went back to Neovim, tried again and it started working :D. I must have called it for an incorrect buffer where sourcekit-lsp was not attached. Thank you for the help!
I wonder if there is a support for
textDocument/inlayHint
. It looks like there is because I found this PR: #465However, when I try to request data I get:
It’s also weird that VS Code somehow is able to get those hints from the LSP.
The text was updated successfully, but these errors were encountered: