workspace.workspaceFolders client capability missing dynamic registration support

[MariaSolOs]

The protocol currently specifies that the workspace.workspaceFolders client capability is simply a boolean, but then it isn't clear how a server can tell whether an editor supports dynamic registration for the workspace/didChangeWorkspaceFolders notification.

[MariaSolOs]

In fact, it isn't clear which client capability maps to the workspace/didChangeWorkspaceFolders request. Based on the VS Code implementation it seems that editors that supports workspace/workspaceFolders should also support workspace/didChangeWorkspaceFolders (?).

[dbaeumer]

Yes, this was always the assumption. If a client supports workspace folder it supports change notifications. I would like to keep it that way and rather doc in the spec since changing this might break existing servers.

[MariaSolOs]

Yes, this was always the assumption. If a client supports workspace folder it supports change notifications. I would like to keep it that way and rather doc in the spec since changing this might break existing servers.

Okay I understand that, but there's still no information in the client's capabilities about dynamic registration support for the workspace/didChangeWorkspaceFolders notification.