nvimdev / nvimdev/lspsaga.nvim
"No information available" when calling hover_doc
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Is supposed that using the ++quiet mode the notification saying "No information available" should disappear, but it doesn't.
I don't know if is only happening to me.
keymap.set("n", "<leader>K", "<cmd>Lspsaga hover_doc ++quiet<CR>", opts) -- show documentation for the cursor
I'm using the last published version.
This is related to #1015.
Screen capture
Steps to reproduce
- Open a react typescript file
- Call
Lspsaga hover_doc ++quietover the component name (which is typed properly).
Expected behavior
Do not see any notification or message saying "No information available", just see the hover_doc floating box.
Neovim version (nvim -v)
NVIM v0.9.1 Build type: Release LuaJIT 2.1.0-beta3
lspsaga commit
5fa17a8
Terminal name/version
iTerm2 build 3.4.20
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
Start by reproducing Lspsaga hover_doc ++quiet over a typed React component in the reported Neovim setup, then trace the hover_doc command's quiet-option handling and notification path. Confirm that the floating hover still appears while the “No information available” notification is suppressed, and add or update coverage if the project provides tests for this command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, neovim, react, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100