Skip to content

Commit

Permalink
Fix wrong client capabilities interface listed for document symbol
Browse files Browse the repository at this point in the history
  • Loading branch information
bmwalters committed Nov 23, 2019
1 parent 9255683 commit 3002e2e
Showing 1 changed file with 24 additions and 2 deletions.
26 changes: 24 additions & 2 deletions _specifications/specification-3-15.md
Expand Up @@ -4179,11 +4179,33 @@ _Client Capability_:
* property type: `DocumentSymbolClientCapabilities` defined as follows:

```typescript
export interface DocumentHighlightClientCapabilities {
export interface DocumentSymbolClientCapabilities {
/**
* Whether document highlight supports dynamic registration.
* Whether document symbol supports dynamic registration.
*/
dynamicRegistration?: boolean;

/**
* Specific capabilities for the `SymbolKind` in the `textDocument/documentSymbol` request.
*/
symbolKind?: {
/**
* The symbol kind values the client supports. When this
* property exists the client also guarantees that it will
* handle values outside its set gracefully and falls back
* to a default value when unknown.
*
* If this property is not present the client only supports
* the symbol kinds from `File` to `Array` as defined in
* the initial version of the protocol.
*/
valueSet?: SymbolKind[];
}

/**
* The client supports hierarchical document symbols.
*/
hierarchicalDocumentSymbolSupport?: boolean;
}
```

Expand Down

0 comments on commit 3002e2e

Please sign in to comment.