Michael Davis 6d0974d9bf lsp: Declare supported SymbolKinds in client capabilities ... In the spec, the `symbolKind` field in `DocumentSymbolClientCapabilities` and `WorkspaceSymbolClientCapabilities` must be set with a `valueSet` containing all supported values. The spec does not default to all values defined in the spec in order to preserve backwards compatibility with older spec versions. Instead of using `None` we need to declare support for all symbols. In the symbol picker code we only use the `SymbolKind` type to print the symbol name. If we get an unknown `SymbolKind` we use the empty string and print nothing, so we satisfy the spec's requirement: > When [symbolKind] exists the client also guarantees that it will > handle values outside its set gracefully and falls back to a default > value when unknown.		2026-04-10 09:19:50 -04:00
..
src	lsp: Declare supported SymbolKinds in client capabilities	2026-04-10 09:19:50 -04:00
Cargo.toml	build(deps): bump tokio in the rust-dependencies group (#15390)	2026-03-04 14:50:31 -05:00