Setup JSON output for domains scripts #184
Open
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.
Hi,
I've started to add some custom output (JSON) for standalone scripts to address the issue #174.
It should be easy to plug other outputs formats like HTML, XML or maybe CSV....
Is this the correct way to implement this ?
I have only done 2 of the domain script to be sure that's the right thing to do before commiting more.
Each of theses scripts got one new arg : the output format. (only applicable if using them as standalone atm. Passing this argument to the runner should probably be implemented after that)
By default, it is set to
console
, with colors outputs and ascii arts enabled.You can set it to
json
to get a clean json output (pipeable into jq for example)Example usage :
Feedback very welcome !