sourcegraph/scip/issues/154 added support for a number of new fields in SCIP's SymbolInformation:
kind
display_name
signature_documentation
enclosing_symbol (what was originally proposed as owner or parent in the linked issue)
On the Java side the sematicdb data already contains the kind (and properties, eg to build an AbstractMethod), but it does not on the Kotlin side.
For both Java and Kotlin:
the semantidb data provides display_name
the signature_documentation is already the first line of the documentation
semanticdb does not specify the owner/enclosing_symbol for locals anymore, although there is already discussion about adding it back in scalameta/scalameta/issues/1540
sourcegraph/scip/issues/154 added support for a number of new fields in SCIP's
SymbolInformation
:kind
display_name
signature_documentation
enclosing_symbol
(what was originally proposed asowner
orparent
in the linked issue)On the Java side the sematicdb data already contains the kind (and properties, eg to build an AbstractMethod), but it does not on the Kotlin side.
For both Java and Kotlin: