Repository navigation
Add PrettyObject to directly render objects as json/yaml - #32
Merged
Merged
Conversation
Contributor
|
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
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.
RATIONALE
The
PrettyObjectclass rendersListorMapobjects. When the output format isjsonoryaml, it renders the objects directly (not putting into table). For other output formats, it creates thePrettyTableusingTableBuilderand renders the table.Rendering the objects directly for
jsonandyamlallows consumers to see the data in a more understandable fashion. It avoids any issues with translating the data to aPrettyTable.CHANGES
Added
PrettyObjectto render data. It has special handling for some data types, andjsonandyamloutput formats.