Title: Quick Fixes not working for TypeScript in Neovim with nvim-lspconfig
Description
Quick Fixes for TypeScript imports are not working in Neovim when using nvim-lspconfig with tsserver. The expected import suggestions do not appear when hovering over unresolved symbols.
Expected Behavior
A list of Quick Fixes should appear, including options to automatically import the unresolved symbol.
Actual Behavior
No Quick Fixes are suggested, and no import options are shown.
Environment
Neovim version: 0.9.2
TypeScript version: 5.3.3
OS: macOS Sonoma 14.3
Screenshots/Logs
LspLog has no errors.
[START][2024-02-15 22:19:01] LSP logging initiated
[WARN][2024-02-15 22:19:01] ...lsp/handlers.lua:137 "The language server astro triggers a registerCapability handler despite dynamicRegistration set to false. Report upstream, this warning is harmless"
Attempted Solutions
I've tried reinstalling nvim-lspconfig and ensuring my tsserver configuration is correct according to the latest documentation.
Checked for any open issues on GitHub related to this problem but found none that resolve my issue.
Additional Context
This issue started occurring after updating to the latest version of nvim-lspconfig. Previous setups with similar configurations did not exhibit this problem.
Steps to Reproduce
Install nvim-lspconfig and configure tsserver according to the documentation.
Open a astro file and use an undefined symbol.
Hover over the symbol and attempt to invoke Quick Fixes.
Describe the Bug
Title: Quick Fixes not working for TypeScript in Neovim with nvim-lspconfig
Description Quick Fixes for TypeScript imports are not working in Neovim when using nvim-lspconfig with tsserver. The expected import suggestions do not appear when hovering over unresolved symbols.
Expected Behavior A list of Quick Fixes should appear, including options to automatically import the unresolved symbol.
Actual Behavior No Quick Fixes are suggested, and no import options are shown.
Environment
Screenshots/Logs LspLog has no errors.
Attempted Solutions
Additional Context This issue started occurring after updating to the latest version of nvim-lspconfig. Previous setups with similar configurations did not exhibit this problem.
Steps to Reproduce