The language-server tool gained a per-operation schema, but nothing chooses it over the old one.
A strict per-operation LSP schema exists alongside the flat one with no selector between them.
What's wrong with this entry?
A new schema for the language-server tool splits it into a separate strict object per operation (goToDefinition, findReferences, hover, documentSymbol, workspaceSymbol, goToImplementation, prepareCallHierarchy, incomingCalls, outgoingCalls), each with its own field descriptions, so arguments are validated per operation instead of against one flat shape. The old flat schema is still in the build and nothing in this group decides which one the tool presents.
- The workspaceSymbol variant drops the "(workspaceSymbol only)" qualifier from its
querydescription, since the field now exists only there.
The symbol name or partial name to search for. Most language servers return no results for an empty query.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.