Tabular Outputs - Expand support for "all columns" (and other shortcuts) #213
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.
Synopsis
Many subcommands produce some kind of tabular data-set for output. The default tables are designed to be generally useful. But for more advanced cases, the output can be customized to use particular columns and output-formats.
This branches provides more options to help with those advanced. In particular, the option
-a
(--all-columns
) can help inspect output. Additionally, it reduces some duplicate code to further standardize behavior of more commands.(Note that
-a
is a bit different from-v
. "Verbose" output enables more logging throughout the execution of the job. "All Columns" enables a full view of the final result-set.)Technical Details
This includes some work on extractions, refactorings, helpers. The big one is
sendStandardTable()
. This is likesendTable()
used here-to-fore, but it enforces some standardized behaviors for column-selection and sorting.