flo-l/jsonpp-rs

UNIX style tool to pretty print json

jsonpp-rs's Issues

Feature request: adds an end break line (-w)

Hi.

Consider the following test:

[user@host ~]$ curl -s http://localhost:8080/fiscalidade/v1/version | jsonpp
{
  "status": "ok",
  "result": {
    "major": 0,
    "minor": 6,
    "patch": 2
  }
}[user@host ~]$

Notice the output JSON doesn't contains an end empty line. With this new feature, it would allow to print as:

[user@host ~]$ curl -s http://localhost:8080/fiscalidade/v1/version | jsonpp <some-option-here>
{
  "status": "ok",
  "result": {
    "major": 0,
    "minor": 6,
    "patch": 2
  }
}
[user@host ~]$

The cURL tool contains a -w feature that is possible to do something like this:

[user@host ~]$ curl -s -w '\n' http://localhost:8080/fiscalidade/v1/version
{"status":"ok","result":{"major":0,"minor":6,"patch":2}}
[user@host ~]$ 

so, a good option to jsonpp tool could be:

[user@host ~]$ curl -s http://localhost:8080/fiscalidade/v1/version | jsonpp -w '\n'
{
  "status": "ok",
  "result": {
    "major": 0,
    "minor": 6,
    "patch": 2
  }
}
[user@host ~]$

WDYT?

Option to print comma at the beginning of the line

It would be cool to have an option for the formatter to print the comma at the beginning of the line. So instead of

{
  "key1": "value1",
  "key2": "value2"
}

it should print

{
  "key1": "value1"
  , "key2": "value2"
}

This would help when the file is version controlled because adding a new value in the first case would cause a 2 line diff while adding a value in the second case, would only cause a single line diff:

{
  "key1": "value1",
  "key2": "value2",
  "key3": "value3"
}

vs.

{
  "key1": "value1"
  , "key2": "value2"
  , "key3": "value3"
}

This is inspired by the format elm decided to use. Actually for better formatting, having the opening bracet and the first key/value pair in the same line would be nice to:

{ "key1": "value1"
, "key2": "value2"
}

You could implement a format optimized for version controll while still be human readable

Add Benchmarks

As Rust is so strong performance-wise it'd be cool to be among the fastest json pretty printers out there.

Maybe as a start three files with ~1Kb, ~1MB and ~1GB..

I'd accept a PR anytime!

Add optional color support

Json syntax highlighting would be a great addition to the library. One possibility is highlighting by default when stdout is a tty and no highlighting when stdout is a pipe or file. A --color flag could be used to override default behavior

Read from stdin if a path is not given

This would be immensely useful for piping (curl https://...json | pp)

Support files with line delimited json entries

While technically not a valid json file, I've come across many files where each line is a separate valid json object. jq is an example of a command line tool that handles this gracefully by parsing and processing each line in turn. It would be nice if pp_rs handled these types of files

Add jq style support?

See jq.