-
Notifications
You must be signed in to change notification settings - Fork 92
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
feat: Introduce integrated terminal #3079
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3079 +/- ##
=======================================
Coverage 92.99% 92.99%
=======================================
Files 116 117 +1
Lines 12008 12026 +18
Branches 2753 2691 -62
=======================================
+ Hits 11167 11184 +17
- Misses 839 840 +1
Partials 2 2 ☔ View full report in Codecov by Sentry. |
Quality Gate failedFailed conditions |
…terminals 😋 Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
525170c
to
4f7dd21
Compare
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: zFernand0 <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
…nto feat/int-term Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
packages/zowe-explorer/__tests__/__unit__/tools/ZoweTerminal.unit.test.ts
Fixed
Show fixed
Hide fixed
packages/zowe-explorer/__tests__/__unit__/tools/ZoweTerminal.unit.test.ts
Fixed
Show fixed
Hide fixed
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
packages/zowe-explorer/__tests__/__unit__/commands/ZoweCommandProvider.unit.test.ts
Fixed
Show fixed
Hide fixed
packages/zowe-explorer/__tests__/__unit__/commands/ZoweCommandProvider.unit.test.ts
Fixed
Show fixed
Hide fixed
packages/zowe-explorer/__tests__/__unit__/commands/ZoweCommandProvider.unit.test.ts
Fixed
Show fixed
Hide fixed
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
…nto feat/int-term Signed-off-by: Fernando Rijo Cedeno <[email protected]>
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.
Thanks @zFernand0 for this awesome enhancement! A few questions:
- I was a bit surprised to still see a quickpick when I try to issue MVS/TSO/USS command, as I expected to be taken straight to a terminal. I assume this behavior is intended because we want to avoid too much of a breaking change in UX. Curious if it would make sense to include an item in the quickpick to "Open MVS/TSO/USS terminal" in case someone prefers to go directly to there?
- Should we "gray out" placeholder text like the first line
Welcome to the integrated terminal...
to make it easier to distinguish from command output? - For SSH commands, should we strip off
$
from the front of the response? It may look a bit weird and cause alignment issues for output of some commands likels -la
:
$ ibmuser.p12 ibmuser-crt.pem test2.txt
a.out ibmuser-crt2.pem test23
bash start.sh testHex.txt
This comment was marked as outdated.
This comment was marked as outdated.
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
- fix: remember ssh directory after running initial command - feat: added command history to every issued command withing the iTerm Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
dependencies: - disposablestack 1.1.5 + disposablestack 1.1.6 devDependencies: - @types/jest 29.5.12 + @types/jest 29.5.14 - @types/mocha 10.0.6 + @types/mocha 10.0.9 - @types/node 18.19.33 + @types/node 18.19.64 (22.9.0 is available) - @types/vscode 1.89.0 + @types/vscode 1.95.0 - @vscode/vsce 3.1.0 + @vscode/vsce 3.2.1 - esbuild-loader 4.1.0 + esbuild-loader 4.2.2 - eslint 8.57.0 + eslint 8.57.1 (9.14.0 is available) deprecated - jest-stare 2.5.1 + jest-stare 2.5.2 - mocha 10.4.0 + mocha 10.8.2 - ts-jest 29.1.2 + ts-jest 29.2.5 - tsx 4.10.4 + tsx 4.19.2 - typescript 5.4.5 + typescript 5.6.3 - webpack 5.94.0 + webpack 5.96.1 Signed-off-by: Fernando Rijo Cedeno <[email protected]>
…nto feat/int-term Signed-off-by: Fernando Rijo Cedeno <[email protected]>
…nto feat/int-term Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
|
|
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Reminder: This pull request has a merge-by date coming up within the next 24 hours. Please review this PR as soon as possible. @t1m0thyj @JillieBeanSim @awharn @rudyflores @traeok @adam-wolfe @SanthoshiBoyina1 @likhithanimma1 |
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.
Thanks Fernando for all your work on this, this looks awesome! I had a couple requests about moving the history settings for these terminals as well as a question about the TypeScript error in #3298
"typescript": "^5.3.3", | ||
"webpack": "^5.94.0", | ||
"ts-jest": "^29.2.5", | ||
"tsx": "^4.19.2", | ||
"typescript": "^5.6.3", |
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.
Comparing the outputs from CI in this PR and another recent PR, I think the update from [email protected] -> [email protected]
is causing the issue described in #3298. I'm wondering if we should hold off on the TypeScript update until the cause is identified/resolved 🤔
/** | ||
* Issues a TSO Command without the need for account information | ||
* | ||
* @param {string} command | ||
* @param {zostso.IStartTsoParms} parms | ||
* @returns {Promise<zostso.IIssueResponse>} | ||
* @memberof ICommand | ||
*/ | ||
issueTsoCmdWithParms?(command: string, parms?: zostso.IStartTsoParms): Promise<zostso.IIssueResponse>; | ||
|
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.
Question for my own edification: Was this added to prevent overwriting the behavior that's in place for existing issueTsoCommandWithParms
implementations? I noticed that the function signatures are the same for both in this interface.
MvsCommands = "zowe.commands.mvs.history", | ||
TsoCommands = "zowe.commands.tso.history", | ||
UssCommands = "zowe.commands.uss.history", |
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 can add these as readable/writable keys for local storage access in #3299 once they're available in main
😋
"zowe.commands.mvs.history": { | ||
"default": { | ||
"persistence": true, | ||
"history": [] | ||
}, | ||
"description": "%zowe.commands.mvs.history%", | ||
"scope": "application" | ||
}, | ||
"zowe.commands.tso.history": { |
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.
We currently keep history for Data Sets, USS and Jobs in local storage. Should these be moved into local storage to keep all the "history settings" in one place? If these are moved, I believe the logic would need updated to grab these from local storage.
ZoweLogger.info(this.operationCancelled); | ||
return; |
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.
Is this log message needed? If so, can we make it more specific to point out exactly what operation was cancelled? From the perspective of a user reading the output channel, all that would be printed is [INFO] Operation cancelled
.
const noProfAvailable = vscode.l10n.t("No profiles available"); | ||
ZoweLogger.info(noProfAvailable); |
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.
Similar request to the operation cancelled log message - if we want to log a message here, additional context could help surface an issue if no profiles are available.
Signed-off-by: Fernando Rijo Cedeno <[email protected]>
Two things I've run into with issuing TSO commands:
|
Proposed changes
Introduces the MVS, TSO, and Unix command handlers as integrated terminals
Release Notes
Milestone: 3.1.0
Changelog: Introduces the MVS, TSO, and Unix command handlers as integrated terminals
Types of changes
Checklist
General
yarn workspace vscode-extension-for-zowe vscode:prepublish
pnpm --filter vscode-extension-for-zowe vscode:prepublish
Code coverage
Deployment
Further comments
Merged and published: