Consider splitting DocumentSymbol and Breadcrumbs into separate requests

[matklad]

Currently, DocumentSymbol request is used for three different UI concepts:

• file outline
• fuzzy symbol search in file
• breadcrumbs

It seems like breadcrumbs in particular could benefit from a dedicated request as it then becomes possible, to, eg, include control flow information with them:

[dbaeumer]

@jrieken did this come up for you as well?

[olegtk]

Can't this be done already with textDocument/foldingRange?

[jrieken]

Can't this be done already with textDocument/foldingRange?

No.

@jrieken did this come up for you as well?

Yes it did come up with JSON which often has a massive (and therefore capped) outline.

VS Code makes sure you use a single request for breadcrumbs and outline, so making these independent would actually double the amount of requests (since both are on by default). Also, I don't think (I might wrong tho) that there is much saving in computation-cost when asking for breadcrumbs only. The only savings would be in bandwidth, but again only if outline is off.

[matklad]

I was thinking about UI savings: I don‘t want to see if (true) in the document symbols view, for example. Another way to achieve that would be to add some kind of „breadcrumbs only“ flag to the DocumentSymbol.