Skip to content
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

Is textDocument/inlayHint supported? #1088

Closed
wojciech-kulik opened this issue Feb 24, 2024 · 3 comments
Closed

Is textDocument/inlayHint supported? #1088

wojciech-kulik opened this issue Feb 24, 2024 · 3 comments

Comments

@wojciech-kulik
Copy link

wojciech-kulik commented Feb 24, 2024

I wonder if there is a support for textDocument/inlayHint. It looks like there is because I found this PR: #465

However, when I try to request data I get:

Method not found: textDocument/inlayHint

It’s also weird that VS Code somehow is able to get those hints from the LSP.

@ahoppen
Copy link
Member

ahoppen commented Feb 24, 2024

Tracked in Apple’s issue tracker as rdar://123555008

@adam-fowler
Copy link
Contributor

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.

@wojciech-kulik
Copy link
Author

wojciech-kulik commented Feb 24, 2024

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants