-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Map all symbol kinds to vscode.SymbolKinds #1911
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks for your contribution!
@akshita31 Before we merge this, do you mind pulling the branch and verifying the behavior? |
@rchande how do we add a test for this behavior? |
@TheRealPiotrP Well, if we had per-feature unit tests, that would be a good place to add these tests. However, we're doing approximately the same mapping in |
@rchande The type "Delegate" is missing here. It is not present in SymbolKind as well. Should we go ahead and add that ? |
@akshita31 Sure. What icon does it show up with now? Note that there's no VSCode icon for "Delegate" https://code.visualstudio.com/docs/extensionAPI/vscode-api#SymbolKind |
Currently it is defaulting to a class type, hence we are getting a symbol for the class only. |
The change does make the functionality a lot better. @craig006 could you add a case for |
Assuming @craig006 doesn't have the time at the moment, can we take this PR and make the change @akshita31 suggested separately? |
Thanks for your contribution @craig006! This has been merged. |
Fixes this issue:
#1907