You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case where I need to request DocumentSymbol of large number of files on one go for my Vscode Extension.
I have looked into LSP documentation and Vscode's, and as far as I could tell... there does not seem to be a supported mechanism to do this directly. I looked at:
Workspace request is not useful for me as it does not return the DocumentSymbol hierarchy which is crucial for my work.
I resorted to implementing some sort of batch processing where I go over all the source files I need, sending a DocumentSymbol request for each. The solution works with different languages I tried, but it is far from perfect and I am wondering if LSP community would consider supporting such a feature in the near future?
Considering the performance load it would put on servers, I suppose it could be implemented with some sort of latent response mechanism.
I have a use case where I need to request
DocumentSymbol
of large number of files on one go for my Vscode Extension.I have looked into LSP documentation and Vscode's, and as far as I could tell... there does not seem to be a supported mechanism to do this directly. I looked at:
Workspace request is not useful for me as it does not return the
DocumentSymbol
hierarchy which is crucial for my work.I resorted to implementing some sort of batch processing where I go over all the source files I need, sending a
DocumentSymbol
request for each. The solution works with different languages I tried, but it is far from perfect and I am wondering if LSP community would consider supporting such a feature in the near future?Considering the performance load it would put on servers, I suppose it could be implemented with some sort of latent response mechanism.
Note: there's a related request on vscode repo.
Any thoughts or tips, please?
Thank you
Mujtaba
The text was updated successfully, but these errors were encountered: