mirror of https://gitee.com/openkylin/libvirt.git
7197e5fd3f
json_reformat uses two spaces for when indenting nested objects, let's do the same. The result of virJSONValueToString will be exactly the same as json_reformat would produce. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> |
||
|---|---|---|
| .. | ||
| README | ||
| input-data-admin-nomdns.json | ||
| input-data-admin-server-names.json | ||
| input-data-anon-clients.json | ||
| input-data-client-ids.json | ||
| input-data-client-timestamp.json | ||
| input-data-initial-nomdns.json | ||
| input-data-initial.json | ||
| input-data-no-keepalive-required.json | ||
| output-data-admin-nomdns.json | ||
| output-data-admin-server-names.json | ||
| output-data-anon-clients.json | ||
| output-data-client-ids.json | ||
| output-data-client-timestamp.json | ||
| output-data-initial-nomdns.json | ||
| output-data-initial.json | ||
| output-data-no-keepalive-required.json | ||
README
virnetservertest data files =========================== The various input-data-*.json files are a record of all the historical formats that libvirt has been able to produce data for. Everytime a new field is added to the JSON output, a *new* input data file should be created. We must not add new fields to existing input-data files, nor must we ever re-structure them if code changes, as we must check new code handles the legacy formats. The various output-data-*.json files are the record of what the *new* JSON output should look like for the correspondingly named input-data file. It is permissible to change the existing output-data-*.json files if the format we save in is updated.