Fails on already pretty JSON about jsonpp HOT 9 CLOSED

I just noticed that you said in #1 that you won't support newlines in JSON. That at least seems worth documenting, and perhaps including in the error message.

(Note I'm using the Homebrew version, which doesn't has an empty --help:

Usage of jsonpp:

from jsonpp.

I had this issue too. Accepting newlines or giving a better error message would be great

from jsonpp.

I also get an empty help message with --help (using homebrew) and I think it would be nice to take already pretty json and keep it that way. I would like to be able to keep my json file pretty even though I'm still modifying it and not have to put everything on one line. If this is a feature that you'd support I'd be glad to help contribute back.

from jsonpp.

Yeah, I think in its current state the behavior is broken.

Piping in already pretty (or non-crunched) JSON via stdin results in an error... pretty unexpected...

from jsonpp.

I just run into this also. Is there a good reason for parsing each line instead of the whole input? The only use case i can come up with is indenting output where each line is a separate JSON string.

A workaround is to replace new lines, e.g:

curl ... | tr "\n" " " | jsonpp

from jsonpp.

Just went through the same exercise this afternoon, every file I tried to parse exited with:

ERROR: Broken json on line 1, char 2: unexpected end of JSON input
Context: {

Went back to jsonlint which thinks my JSON is just dandy.

It's documented, but it still seems like an odd behavior.

from jsonpp.

For people ending up here: try the program jq, e.g. cat file.json | jq .

from jsonpp.

@wader, thanks

from jsonpp.

@da-mobenga 👍

from jsonpp.