Enable delayOpenNotifications=true with LSP client vNext to prevent redundant didOpen/didClose notifications to server

See microsoft/vscode-languageserver-node#848 (comment)

textSynchronization: {
	delayOpenNotifications: true,
},

This will prevent redundant didOpen/didClose events being sent from VS Code to the LSP server when holding Ctrl and hovering over something (which triggers some work for the open file, such as sending outline notifications etc.).

Enable delayOpenNotifications

This appears to have caused a bug where open notifications will have "future" versions of the content when a file is created from a code action (see dart-lang/sdk#62209).

For now, I'm reverting the flag (but keeping the vNext client for simplicity) and will fail an issue in the LSP client.

Disable delayOpenNotifications due to bug

Bump to LSP client vNext

Navigation Menu

Repository navigation

Enable delayOpenNotifications=true with LSP client vNext to prevent redundant didOpen/didClose notifications to server #5176

7 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Enable delayOpenNotifications=true with LSP client vNext to prevent redundant didOpen/didClose notifications to server #5176

Description

Activity

7 remaining items

DanTup commented on Dec 9, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions