The consecutive JSON documents of an answer's body as the library reads
them (big ids as text): a streamed answer's chunks, in the order the server
sent them. A body that stops splitting or parsing midway keeps the chunks
before the break, and a body that does not start as JSON gives []. A
screen that acts on each chunk, as the app does when it arrives, reads them
here; the merged answer the request returned has lost the boundaries.
The consecutive JSON documents of an answer's body as the library reads them (big ids as text): a streamed answer's chunks, in the order the server sent them. A body that stops splitting or parsing midway keeps the chunks before the break, and a body that does not start as JSON gives
[]. A screen that acts on each chunk, as the app does when it arrives, reads them here; the merged answer the request returned has lost the boundaries.