Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support right click context for viewer nodes #208
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
Support right click context for viewer nodes #208
Changes from 4 commits
cb37fd6
6198969
6cd2ad0
d381c90
3fbdb78
f2f740b
cba229e
c87df7d
2949f08
3efc15b
9f71db3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
revealFileInOS -> revealInExplorer
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.
revealInExplorer
is not appropriate since it is related to two built-in commands in VS Code:revealInExplorer
andgit.revealInExplorer
- They all refer to the meaning of "Reveal the file node in VS Code File Explorer", not the OS explorer.In contrast,
revealFileInOS
is a built-in command of VS Code to open a file in OS explorer, and our command just forwards the dependency node's uri to it, so this naming would be fine.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.
so why not to mount the VS Code builtin command to the dependency explorer directly?
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.
It would be best that we could mount the builtin command directly.
But the builtin command accepts a
Uri
argument, where context entry specified inpackage.json
only allows for passing aExplorerNode
to the command binding.(The
TreeItem.command
property can indeed specify the argument to be passed, but this is not the case withview/item/context
entry)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.
It seems VS Code provides different names in different OSes, could you check whether we need keep consistent?
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.
Sorry for I didn't notice this comment...
As this file shows, VS Code does provide different names here:
Reveal In Explorer
Reveal In Finder
Open Containing Folder
And the Chinese translation uses that localization:
Currently I have no knowledge of how to utilize the localization here according to OS...
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.
Currently i'm OK to keep the same one, if there is user complaint, then fix it.
A workaround is add three difference commands, and use when clause to enable the correct one.