Fernando Rijo Cedeno comments

Results 178 comments of


                                            Fernando Rijo Cedeno

CLI options are not alphabetically sorted making help hard to navigate

I believe this might be a good first issue against the `next` branch 😋 Contributors only need to look for any option definition and make sure to sort by option...

prompting inconsistencies

zowe/zowe-cli#1939 might be related to this 😋

Display message from "causeError" in rest client

Hey @dkelosky, Is this still an issue with the OPS plugin?

[v2] Command handler unit tests require a lot of mocks

After a short discussion, we wanted to reduce code duplication. This might be a good enhancement for the cli-test-utils package. We could add a few clever ways to mock these...

Token gets output to Imperative log in plain text

@t1m0thyj, do we want to remove it from the trace level log? If so, should this be a `good first issue` ?

Token gets output to Imperative log in plain text

I think that's good enough. However, Don't we want to deprecate tokenType and tokenValue? zowe/zowe-cli#1937

Regenerating schema after plugin install may not include all profile types

Related to: - https://github.com/zowe/vscode-extension-for-zowe/issues/2508

Inconsistent error messages when credentials fail to save error

We may want to standardize on the prettier error message. `secureSaveError` Marking as good first issue.

Plugin install command not using TextUtils.wordWrap

This is still an issue: https://github.com/zowe/imperative/blob/26bb8c0e1ff703eb5365d14de13859398614153b/packages/imperative/src/plugins/cmd/install/install.handler.ts#L95-L102

Failed to load schema for profile type `sample` when default doesn't exist

Here is what the error may look like ```bash ProfInfoErr: Failed to load schema for profile type sample at ProfileInfo.mergeArgsForProfile (~/node_modules/@zowe/imperative/src/config/src/ProfileInfo.ts:803:19) at ~/test.ts:21:31 { mDetails: { errorCode: 'LoadSchemaFailed', msg: 'Failed...