nvimdev / nvimdev/lspsaga.nvim
[Enhancement] Better `Lspsaga subtypes` and `Lspsaga supertypes` LSP filtering
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
When running the following commands:
Lspsaga subtypesLspsaga supertypes
a pop-up appears asking to select the wished LSP to perform the TypeHierarchy request.
For example, in the case of Python** it is possible in my buffer to select between:
basedpyrightruffcopilot
copilot wouldn't make sense and it is suggested on every buffer where it is active.
To solve this, I would propose for example to check if the LSP attached to the buffer supports the TypeHierarchy capability, before showing it in the pop-up.
Also, maybe it would be technically possible to merge all of the results provided by the remaining LSPs?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the implementation behind Lspsaga subtypes and Lspsaga supertypes; first trace how attached LSP clients are collected and how the TypeHierarchy request is dispatched. Check how capability filtering could affect the selection popup, then assess whether results from eligible clients can be merged and how completion should be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, neovim
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100