imperative
imperative copied to clipboard
Imperative CLI Framework
https://github.com/zowe/imperative/blob/9a7dde3aa0cd6ba7a32ec4dd970f34b4544e4a3c/packages/cmd/src/doc/processor/ICommandProcessorParms.ts#L79-L80
Currently config JSON files store a single field authToken instead of separate values for tokenType and tokenValue. We should make this consistent everywhere tokenType and tokenValue are currently referenced in...
...to store them as strings. This needs to be handled in both init.handler.ts and secure.handler.ts.
It would be ideal if we could simplify our debug recommendations: 😋 - Before: - `zowe config list --locations --root` - After: - `zowe config list -lr`
- Same as https://github.com/zowe/zowe-cli/issues/1368 PR reference: - https://github.com/zowe/imperative/pull/785
The idea is that if an application developer is using Imperative (e.g. Zowe Explorer) they are able to use this function to retrieve the date formatting directly from the Imperative...
If this (i.e. using past-tense in `changelog.md`) is a standard it should be documented in `contributing.md`. if it is, it's fine to link it _Originally posted by @dkelosky in https://github.com/zowe/imperative/pull/721#discussion_r843199120_
The `zowe config init` will automatically add secured fields. Do we need another parameter for that command that: 1. Prevents adding secure fields or 2. Allows providing a new template...
The `CommandResponse.console.log` function... https://github.com/zowe/imperative/blob/741f24f7246028879317dbd9590b91d7efbdef39/packages/cmd/src/response/CommandResponse.ts#L537-L547 Calls `writeAndBufferStdout` https://github.com/zowe/imperative/blob/741f24f7246028879317dbd9590b91d7efbdef39/packages/cmd/src/response/CommandResponse.ts#L914-L919 Instead of buffering the data, we could Stream it! For example: ```typescript private writeAndBufferStdout(data: Buffer | string) { Readable.from(data).on("data", (chunk) => { process.stdout.write(chunk);...