Also conform to RFC7159

Question

Also conform to RFC7159

czechboy0 opened this issue 9 years ago · 4 comments

czechboy0 commented 9 years ago

http://tools.ietf.org/html/rfc7159
add option to accept fragments, but don't by default (will require changes in the way we ensure reading isn't finished)

Answer 1 · 2016-03-01T15:16:57.000Z

@czechboy0 Jay does not conforms to RFC ? what is missing

Answer 2 · 2016-03-01T15:29:20.000Z

Jay now conforms to RFC4627 (the original JSON standard), but not yet to RFC7159 (updated JSON standard).

The only changes I've noticed are that the new JSON standard allows fragments, whereas the old one only allows array or object as the top level object. So the only changes needed are to add an option to also parse non-container types at the top level.

Do you need fragments on top level?

Answer 3 · 2016-03-02T09:34:02.000Z

maybe I can help with that

Answer 4 · 2016-03-02T09:53:45.000Z

I started on it yesterday but discovered it will require quite lot of changes. So I'd prefer to only add it if people really need it.

Pretty printing on the other hand is up for grabs, that would be great to have!