-
Notifications
You must be signed in to change notification settings - Fork 94
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
Issue a TSO Command #1245
Issue a TSO Command #1245
Conversation
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
@JillieBeanSim I'm not all the way done looking through the code for this yet, but it is functionally looking very good so far, and all unit/expected integration tests are passing. A couple small things I was wondering about:
|
Signed-off-by: Billie Simmons <49491949+JillieBeanSim@users.noreply.github.com>
@lauren-li These comments have been addressed for this PR, but having the I moved the prompt for acctNum to before the command prompt, but this prompt is specific to |
This is amazing! Thank you for working on this @JillieBeanSim . I just skimmed through the code and tested the functionality itself and it looks good for me. I think there are additional features that I would like to see in the future. I can open a separate issue for that.
But overall, it works for me. Thank you! |
@jellypuno by persisted MVS & TSO commands do you mean the output window? I just noticed the dropdown will have 2 of the same |
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.
I moved the prompt for acctNum to before the command prompt, but this prompt is specific to zosmf profiles at this moment as FTP doesn't have it implemented yet and RSE doesn't require it. Without being able to test other scenarios I am leaving it up to the extender to obtain their account number if needed in their API file vs unnecessarily prompting for it if not needed and confusing the user. If a time comes that we may need to extend this scenario we can address it in the future.
This sounds good to me. Thanks @JillieBeanSim for addressing my comments!
I also agree we probably want to separate the persisted commands for MVS vs TSO (i.e. the ones that appear in the dropdown), as well as their outputs, but I think it's fine to do this in a future PR. The TSO command functionality itself seems to be working very well. All unit and expected integration tests (plus the command submission test) are still passing for me.
This PR looks good to me!
Note: Per previous scrums, the Theia tests will be investigated and fixed in a separate PR.
Signed-off-by: Billie Simmons 49491949+JillieBeanSim@users.noreply.github.com
Proposed changes
Be able to issue a TSO command using Zowe Explorer
Release Notes
Milestone: 1.14.0
Changelog: Added
Issue TSO Command
UI capability via right-click action on tree session and also available in the command palate. New APIICommand
withissueTsoCommand()
andissueMvsCommand()
for consumption by Zowe Explorer Extenders.NOTE see #1245 (comment) for information about new TSO integration test
Types of changes
What types of changes does your code introduce to Zowe Explorer?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the revieweryarn workspace vscode-extension-for-zowe vscode:prepublish
has been executedFurther comments
For
zosmf
profiles there is a check for atso
profile, if non exist the user is prompted foraccount number
, if one exists it will be automatically used for theaccount number
, and if multiple exist the user will be presented with a list of tso profiles to choose from for theaccount number
.For extenders, I have a check for the new API
ICommand
and if it is not existing I have an Error message that it isNot implemented yet.
With the request to have the validation check change the icon automatically, I have run into an issue since this is available via all 3 trees and I do have the validation setting the icon but this is only showing when the session is clicked on after and not automatically, also a second validation is not run for that session.