Currently when textDocument/documentSymbol is handled where lsp spec response is DocumentSymbol[] | SymbolInformation[] | null. Symbolizer has a return type of Flux<DocumentSymbol> and we assume via org.springframework.dsl.lsp.server.controller.TextDocumentLanguageServerController.documentSymbol(DocumentSymbolParams, JsonRpcSession) returning array of DocumentSymbol's. It's annoying that you can't really handle return type of SymbolInformation.
While we want to create higher lever service interfaces, on lsp level we should still be able to be compatible with a protocol itself.
Currently when
textDocument/documentSymbolis handled where lsp spec response isDocumentSymbol[] | SymbolInformation[] | null.Symbolizerhas a return type ofFlux<DocumentSymbol>and we assume viaorg.springframework.dsl.lsp.server.controller.TextDocumentLanguageServerController.documentSymbol(DocumentSymbolParams, JsonRpcSession)returning array ofDocumentSymbol's. It's annoying that you can't really handle return type ofSymbolInformation.While we want to create higher lever service interfaces, on lsp level we should still be able to be compatible with a protocol itself.