Implement CSV, JSON, YAML, XML, SQL output formats

Create --<$format>-file options, to get the result as script-readable into following formats:

• csv
• json
• yaml
• xml
• sql

Commands

• history
• wot
• …

added Interface enhancement labels

changed milestone to %0.10.0

changed title from implement CLI/JSON/whatever output format to Implement CLI/JSON/whatever output format

changed the description

added CLI label

changed milestone to %0.11.0

added Feature label and removed enhancement label

marked this issue as related to #359

JSON output has been asked by Fred and Poka. It is also an advice of the cli guidelines (#359).

This is available for commands that return a direct output such as wot or history, but not for interactive commands such as tx, or only as final output (useful if --yes is passed). So it would be a per-command option ?

This issue is related with how we manage data in order to display it in a convenient way.

When we will implement it, we should :

• gather the data from Duniter and treat it
• put it in a dict()
• dump dict as JSON output if --json option is passed
• if not, use common tui functions to display the table.

What I mean, is : I think we can write two functions in tui, that will handle almost all table cases we have, with a dict() as input data : the same dict() that would be the JSON output.

changed milestone to %Backlog

changed title from Implement CLI/JSON/whatever output format to Implement CSV/JSON/YAML/XML/SQL output format

changed title from Implement CSV/JSON/YAML/XML/SQL output format to Implement CSV, JSON, YAML, XML, SQL output format

changed title from Implement CSV, JSON, YAML, XML, SQL output format to Implement CSV, JSON, YAML, XML, SQL output formats

changed the description

mentioned in merge request !176

changed the description

marked the checklist item csv as completed

mentioned in commit 67238025

mentioned in merge request !265 (merged)