fix: standardize table output format flag#233
Merged
craicoverflow merged 2 commits intomainfrom Jan 15, 2021
Merged
Conversation
Collaborator
|
🔥 |
wtrocki
approved these changes
Jan 15, 2021
Collaborator
|
For my info. Is that coming as result of alignment meetings? |
Contributor
Author
|
Not that particular one no. I just noticed that there was a difference while using the CLI. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #232
This PR changes "table" and "plain-text" to instead use "plain" as the default value for printing a table.
It is worth nothing that https://clig.dev/#output recommends using individual flags
--json,--yaml,--plain, but this differs from kubectl/oc.