Added 'explorerExclude.showPicker' configuration option, which when f… #13
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.
…alse will NOT show the file picker, but only hide the currently selected item
What's this PR do?
It adds a check in util.js for a configuration/setting option: "explorerExclude.showPicker".
If this is true (or undefined), the extension works as is... if it is false it will NOT show any file picker/choose after clicking 'Add to hidden items...', but will only hide the already selected item.
Where should the reviewer start?
util.js line 383
How should this be manually tested?
Add a vscode setting called: "explorerExclude.showPicker": false and then try to hide any selected item. Set the value to true and confirm the default behavior works.
Any background context you want to provide?
Sure - I was glad to find an extension that would work within Workspaces, as the 'Make Hidden' extension doesn't. Upon using this, I simply want to hide one item at a time in the explorer (main use case), quickly, without being prompted every time, so I thought making this a configuration option made sense.
Definition of Done:
npm test
passes without issue