Allow to invalidate all providers using a single server -> client request.

[dbaeumer]

Currently the are separate methods to invalidate semantic tokens and code lens. Would be good to have one request to invalidate them all since a project wide change usually forces an update of all providers.

[rwols]

I don't entirely understand the idea. Is the idea now that the server should be responsible for invalidating code lenses / semantic tokens / collected code actions ? Because right now, from what I gather from the spec, the client is responsible for deciding when that stateful information is stale.

[rwols]

Aha, I notice now there's a new proposed request workspace/codeLens/refresh.

[dbaeumer]

There are situation where a client can not detect that (e.g. a project configuration file changes). So in these cases a server needs to ask the client to refresh everything.

[matklad]

Interesting observation: today in practice rust-analyzer fiers both /refresh requests on basically every change (and not just on project-wide configuration changes). That is because VS Code pulls for changes for file X only when file X is modified, but it often happens that modifications to a different file Y actually change highlighting and lenses in X. That feels very suboptimal, but, well, not doing this leads to

updates.mp4

[dbaeumer]

@matklad IMO you should file an issue for this against VS Code. If two files are side by side IMO VS Code should pull for semantic tokens with high frequency for the active file and for a lower frequency on the other files.

[matklad]

Done: microsoft/vscode#130486!