LSP: When a server returns SymbolInformation[] in textDocument/documentSymbol, show the containerName
Document symbols can and should support the containerName in the UI.
/** The name of the symbol containing this symbol. This information is for user interface purposes (e.g. to render a qualifier in the user interface if necessary). It can't be used to re-infer a hierarchy for the document symbols. */ containerName?: string;
For example something like this would be helpful to give context to the symbol without affecting the filtering behavior.

About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 39 (24 by maintainers)
We could be absolute nerds and use
⊃(“is superset of”) (or possibly a unicode arrow→)I see it fixed now. Thanks!
SymbolInformation is deprecated in the lsp specification. LSP added the logic to display the
containerNameforSymbolInformartionThe payload for document symbols containing containerName using LSP-pylsp.
I will close this, but feel free to reopen this ticket if something needs to be addressed.
The quick panel could be replaced with a ListInputHandler, which is more compact. Only the labels for the items are in the list in that case, and additional information can be shown at the bottom of the widget (supporting minihtml).
I would suggest
>surrounded by spaces for the separator symbol, i.e.ParentA > ParentB > ParentC. That’s often used in e.g. website navigation to display a hierarchy.