Open sosadchuk opened 1 month ago
Thank you for raising this enhancement request. The community has 90 days to vote on it. If the enhancement receives at least 10 upvotes, it is added to our development backlog. If it receives fewer votes, the issue is closed.
Alternatively, we could also benefit from having a registered command for the Edit Team Config File
option, same as you have for the init (zowe.all.config.init
).
Found similar request #3088 (didn't pop up when I created this one).
Hi,
We're developing a vscode extension that is extending Zowe Explorer if it's available (no hard dependency on the extension is set).
However in both cases we want to provide an aligned experience to our users in terms of initializing & editing the Zowe Team config, meaning the same
Add Profile
button, quick picks, confirmations, notifications and so on:Profiles class extends ProfilesCache with some useful methods like:
Is it possible to move them to the base class by removing view-specific processing?
I believe we reuse almost all of them with minimal changes (commented out trace calls to keep a minimal amount of reused code).
The main entry point that we have is
createZoweSession
, the difference is in the view specific code that is commented out:Of course some of other module methods are imported too, so the final list of files we reuse looks like the following:
P.S. Currently we have to store your project as a subtree, making it not very simple to merge every time we want to sync up, and keeping our update cadence low.
Thanks, Sergei.