We should make sure that the Explorer section of docs.zowe.org has up-to-date information about all the new functions we've been adding :)
@IgorCATech and I decided to make a list of all the functions, and then we can check what's up with the docs. So yeah here's the issue for that :)
Feel free to add whatever.
Cool beans @katelynienaber Ok, so here's the list so far:
@zdmullen Surely, you know more ;) Feel free to add them
On another but related note, the videos are outdated, so it would be nice to work on them at some point.
Haven't checked if docs have these yet, just brainstorming, some were mentioned by @IgorCATech:
But we could list/mention them as functionality that Explorer supports
We could link to the IBM docs in our docs XD
jobActions.modifyCommand
dsActions.allocateLike
jobActions.downloadSpool
jobActions.downloadJcl
dsActions.hMigrateDataSet
dsActions.hRecallDataSet
jobActions.getSpoolContent
MvsCommandHandler.getInstance().issueMvsCommand
dsActions.submitJcl
dsActions.submitMember
dsActions.showDSAttributes
Probably clear from how VSCode functions:
dsActions.refreshPS
dsActions.openPS
dsActions.copyDataSet
dsActions.pasteDataSet
node.openUSS
ussFileProvider.rename
Probably clear from context menu text:
dsActions.createMember
datasetProvider.rename
dsActions.deleteDataset
ussActions.refreshAllUSS
node.refreshUSS
ussActions.refreshUSSInTree
node.deleteUSSNode
ussFileProvider.deleteSession
ussActions.copyPath
ussFileProvider.editSession
ussFileProvider.removeFavorite
jobsProvider.delete
jobActions.stopCommand
jobActions.refreshAllJobs
jobActions.refreshJobsServer
ussFileProvider.addFavorite
jobActions.setOwner
jobActions.setPrefix
jobsProvider.filterPrompt
ussActions.createUSSNode
ussActions.uploadDialog
dsActions.uploadDialog
dsActions.createFile
These functions are only used internally:
zowe.setJobSpool - To focus the tree view on a single job
ussActions.changeFileType - To change file type (ex. to try re-downloading a file as binary)
We tend not to document enhancements of UI. Good UI/UX needs no doc :P
So thanks for creating this. One thing I want to stress however, is that we do not get in the habit of creating these kinds of issues, but instead check up on the development as it's happening and make sure we maintain the doc continuously. This also depends on contributors actively marking their PRs as "Updates to documentation" in the checklist.
Closing this in favor of the doc epic