Thank you. Can you create a separate getHierarchicalDocumentSymbols method in the DocumentSymbolsProvider for the new format, while retaining the old format for compatibility? You can add a check in the server.ts to check configManager.getClientCapabilities()?.textDocument?.documentSymbol?.hierarchicalDocumentSymbolSupport to know whether we can provide the new format.

Also, since the server controls the hierarchy in the new format. We need to manually merge the result from TypeScript and HTML. Otherwise, the variables that are inside the template are no longer being marked as under a component/HTML tag. This can be done in the PluginHost. But this is a bit complex for a first-time contributor, so feel free to ask for direction if you can't figure out a way to do it. Or we can also add it in a later PR.

Thank you. Can you create a separate getHierarchicalDocumentSymbols method in the DocumentSymbolsProvider for the new format, while retaining the old format for compatibility? You can add a check in the server.ts to check configManager.getClientCapabilities()?.textDocument?.documentSymbol?.hierarchicalDocumentSymbolSupport to know whether we can provide the new format.

So return SymbolInformation[]?

Also, since the server controls the hierarchy in the new format. We need to manually merge the result from TypeScript and HTML. Otherwise, the variables that are inside the template are no longer being marked as under a component/HTML tag. This can be done in the PluginHost. But this is a bit complex for a first-time contributor, so feel free to ask for direction if you can't figure out a way to do it. Or we can also add it in a later PR.

Yeah, I just noticed that it also messed up snippets, will take a look.

So return SymbolInformation[]?

Returns DocumentSymbol[] if the LSP client supports the new format.

// packages/language-server/src/server.ts
connection.onDocumentSymbol((evt, cancellationToken) => {
    if (
        configManager.getClientCapabilities()?.textDocument?.documentSymbol
            ?.hierarchicalDocumentSymbolSupport
    ) {
        return pluginHost.getHierarchicalDocumentSymbols(evt.textDocument, cancellationToken);
    }
    return pluginHost.getDocumentSymbols(evt.textDocument, cancellationToken);
});

Ok, so now it sorts and builds the hierarchical tree manually based on the symbol range.
And since it does it manually anyway, it's better to return the flat SymbolInformation[] in the plugins.

Typescript inside HTML and Snippets are still messed up, though, I'm not sure where to look to fix it.