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
Is your feature request related to a problem? Please describe.
Currently it's almost impossible to see which target a file belongs to, especially if there two versions of the same file.
This is especially problematic with the custom search in VS Code, but with the default symbols search you can only see the full path, which is still not ideal.
This would also benefit other editors.
Describe the solution you'd like
We should print the target for each symbol shown.
Describe alternatives you've considered
Using the default VS Code symbols search and see the path.
Additional contex
Search terms
workspace symbol target
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently it's almost impossible to see which target a file belongs to, especially if there two versions of the same file.
This is especially problematic with the custom search in VS Code, but with the default symbols search you can only see the full path, which is still not ideal.
This would also benefit other editors.
Describe the solution you'd like
We should print the target for each symbol shown.
Describe alternatives you've considered
Using the default VS Code symbols search and see the path.
Additional contex
Search terms
workspace symbol target
The text was updated successfully, but these errors were encountered: