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

feat(lsp): support vim.lsp.ListOpts for typehierarchy() #28483

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tom-anders
Copy link
Contributor

No description provided.

runtime/doc/lsp.txt Outdated Show resolved Hide resolved
runtime/lua/vim/lsp/handlers.lua Outdated Show resolved Hide resolved
@tom-anders
Copy link
Contributor Author

Thanks for the review!

runtime/doc/lsp.txt Outdated Show resolved Hide resolved
@tom-anders
Copy link
Contributor Author

Latest push fixes the lua warning about a shadowed parameter. Is there any way to disable the next.txt check? Or do we just ignore it?

@glepnir
Copy link
Member

glepnir commented May 1, 2024

news for feat change scope will skip it.

@tom-anders
Copy link
Contributor Author

news for feat change scope will skip it.

Right, but I think feat is appropiate here, isn't it? Or should this be a fix instead?

runtime/lua/vim/lsp/handlers.lua Outdated Show resolved Hide resolved
runtime/lua/vim/lsp/handlers.lua Outdated Show resolved Hide resolved
@tom-anders
Copy link
Contributor Author

Thanks for the review again!

I noticed that the loclist key to vim.lsp.ListOpts is not actually documented, but most LSP handlers still support it (e.g. references, documentSymbols, workspaceSymbol). There are some LSP handlers though that do not support it (declaration, definition, typeDefinition, implementation). Should I fix this in this PR as well, or maybe open a new one instead?

tom-anders added a commit to tom-anders/neovim that referenced this pull request May 4, 2024
tom-anders added a commit to tom-anders/neovim that referenced this pull request May 4, 2024
tom-anders added a commit to tom-anders/neovim that referenced this pull request May 4, 2024
@tom-anders
Copy link
Contributor Author

All suggestions should be applied now, I moved the cleanup to a new PR: #28637

tom-anders added a commit to tom-anders/neovim that referenced this pull request May 7, 2024
tom-anders added a commit to tom-anders/neovim that referenced this pull request May 7, 2024
tom-anders added a commit to tom-anders/neovim that referenced this pull request May 7, 2024
tom-anders added a commit to tom-anders/neovim that referenced this pull request May 7, 2024
tom-anders added a commit to tom-anders/neovim that referenced this pull request May 7, 2024
tom-anders added a commit to tom-anders/neovim that referenced this pull request May 7, 2024
@tom-anders
Copy link
Contributor Author

(rebased to fix conflicts caused by #28637)

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

Successfully merging this pull request may close these issues.

None yet

8 participants