I assume changes should be made in https://github.com/httptoolkit/httptoolkit-ui

Yes, that's it. You can follow the instructions in the README to run it locally.

I think the changes required are roughly:

Create a new viewable content type (let's call it "JSON records", I think that's the normal name for this kind of thing)
- Content types are defined here
Detect that content type (we don't have a content-type header, so we can't know, but we can sniff it to add it as an option in the dropdown: any content that starts with { and ends with 0x1e is probably a list of JSON records)
- This is the existing logic to sniff JSON, that would need a separate case to add JSON records instead of JSON if the content ends with 0x1e.
Add support to the editor for formatting & validating this content type as a new Monaco language.
- See httptoolkit/httptoolkit-ui@26ea1b0 for adding custom XML validation as an example.
- We'd need to split the content on 0x1e, then validate each chunk separately, and show errors (just like normal JSON errors) as required.
- We can use jsonc-parser from npm (seems this is what Monaco uses internally for normal JSON) to parse the content, and get error info including the correct line/character positions for any issues.
Create a formatter, to nicely format this content type and make it readable, as we do with JSON:
- The existing JSON format is here, for larger inputs it also uses a worker thread version here
- The language option there controls which Monaco language to use.
- Otherwise it's similar to the validation code: split it into chunks, format each chunk as JSON, stick it back together again.

Does that make sense, more or less?

End of file expected. json(0) in WebSocket message #772

Description