New hover setting requires window reload and does not trigger reload window prompt #10076
Labels
bug
Feature: Auto-complete
fixed
Check the Milestone for the release in which the fix is or will be available.
Language Service
quick fix
Milestone
The new setting to enable/disable hover is passed in the
ServerCapabilities
object in response to LSP initialization. So, if the setting was disabled when the window was loaded, enabling it would require the window to be reloaded to properly initialize LSP to send hover requests.The autocomplete setting is similar. Though, changes to the autocomplete setting do trigger a reload window prompt.
VS Code will merge the results from multiple hover providers, and does something similar (? based on score) with completion. So, I don't believe it's necessary to avoid registering as a hover or completion provider. We could avoid requiring the user to reload the window when either of these settings are changed, by always registering as a provider for them.
The text was updated successfully, but these errors were encountered: