Just for the note that not only JSON, but MongoDB's .bson files store the
same way as series for BSON documents without any separator between.
On Tuesday, August 23, 2016 at 10:23:07 PM UTC+9, Jim Ancona wrote:
>
> This is a pretty common way of streaming JSON objects. See:
> https://en.wikipedi
Perhaps a quick note in the doc that this produces a stream of 0 or more
JSON documents would be helpful? I don't actually think the current doc is
wrong; the data is printed in "JSON format", it's just not a single JSON
document.
On Tue, Aug 23, 2016 at 6:22 AM Jim Ancona wrote:
> This is a pre
This is a pretty common way of streaming JSON objects. See:
https://en.wikipedia.org/wiki/JSON_Streaming
But I agree that it's not part of the JSON standard, nor does it seem to be
standardized anywhere else.
On Mon, Aug 22, 2016 at 9:43 PM, Matt Harden wrote:
> The output is not a valid (singl
The output is not a valid (single) JSON value. It's a number of JSON
values, separated by newlines. jq considers each of these values a separate
"input". There's nothing in the definition of JSON that makes this valid.
On Mon, Aug 22, 2016 at 4:49 PM Edward Muller wrote:
> `go list -json std | j
`go list -json std | jq` does not complain, which is my usual "is my json
valid" test.
On Sat, Aug 20, 2016 at 12:13 PM Lars Tørnes Hansen
wrote:
> I expected that
> go list -json std
> ... would output a valid JSON document, because
> go help list
> writes:
> The -json flag causes the package d
I expected that
go list -json std
... would output a valid JSON document, because
go help list
writes:
The -json flag causes the package data to be printed in JSON format
instead of using the template format.
but ...
- The JSON document is not a JSON array
- Between 2 JSON objects of typ
