You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To Reproduce
Open a folder with a .contextive/definitions.yml file, in Visual Studio with Contextive installed. See the hover panel text. Modify a term definition. Hover to see the hover panel, and see the old definition.
Expected behavior
The hover panel should show the new definition.
Additional context
According to the initialize logs, the language client advertises support for didChangeWatchedFiles with an empty object, which means it doesn't offer dynamic registration.
{
...
"didChangeWatchedFiles": {}
...
}
The text was updated successfully, but these errors were encountered:
chrissimon-au
changed the title
Visual Studio: Definitions don't update in hover panels when the defintions file is updated.
Visual Studio: Definitions don't update in hover panels when the definitions file is updated.
Jul 31, 2024
Describe the bug
In most IDEs when editing the defintions file, the updated definitions appear in the hover panel immediately. In Visual Studio, they don't. This is because Visual Studio supports
didChangeWatchedFile
notifications, but it doesn't support dynamic registration, which is an approach where the language server can nominate which files to watch. See https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#didChangeWatchedFilesRegistrationOptions for details.To Reproduce
Open a folder with a
.contextive/definitions.yml
file, in Visual Studio with Contextive installed. See the hover panel text. Modify a term definition. Hover to see the hover panel, and see the old definition.Expected behavior
The hover panel should show the new definition.
Additional context
According to the
initialize
logs, the language client advertises support fordidChangeWatchedFiles
with an empty object, which means it doesn't offerdynamic registration
.The text was updated successfully, but these errors were encountered: