JSON Hero: Enhanced JSON structure visualization

Post by user3939382 » Wed, Nov 30, 2022, 3:03 AM UTC

Existenceblinks wrote: post #188

user3939382 wrote: post #186

Earlier quoted context omitted.

For my use case that doesn't really help at all. So I'm doing request/response in JSON with a third-party API and I want to programmatically detect if their response is valid, not based on any rules the API can know, but based on the context of my integration. So I use JSON schema to define what valid responses (for my particular application/integration) look like. How I do this now, is to get an example response, au…

I got you now. The data comes from an external source, and then you wanted to infer json schema from it. So I guess the json response from APIs don't have json schema defined for you. But you could define schema from their api documentation, right? It doesn't matter what tool used to generate the json schema, we only care about the result that is the schema so that you can it wherever. Trust me on JSON Schema spec, i…

Post by sieabahlpark » Wed, Nov 30, 2022, 4:47 AM UTC

Post by user3939382 » Wed, Nov 30, 2022, 5:59 AM UTC

yamtaddle wrote: post #172

douglee650 wrote: post #120

JSON is actually a really good format, I disagree with their premise "JSON sucks". Like, sure it's got some use cases it doesn't handle well, but overall there's a reason it won.

The lack of ability to concretely define data structures is a huge pain, both when using it and when writing libraries to process it. You can throw JsonSchema at it, but now you have two problems. Can't use comments to try to work around that deficiency, even just to communicate intent to someone looking at an example record, at least not in vanilla json. Record streaming—basically necessary at anything resembling "s…

Post by jordanmorgan10 » Wed, Nov 30, 2022, 1:38 PM UTC

ilyt wrote: post #161

jordanmorgan10 wrote: post #151

"JSON Sucks". It really doesn't though.

Not as readable as YAML/TOML. Vastly less if unindented. More annoying to write than YAML/TOML, no trailing comma. Yes I'd rank it lower than YAML even with its whitespace annoyances, good editor handle that, JSON is still annoying. Not super compact (althought it's not too bad when compressed). No proper numeric types, just one "sorta int, sorta float, depends on parser, say farewell to NaNs and infinities", you can…

Post by cryptonector » Wed, Nov 30, 2022, 5:28 PM UTC

eallam wrote: post #48

einichi wrote: post #31

My number one requirement for a tool like this is that the JSON content never leaves the machine it's on. I can only imagine the kind of personal information or proprietary internal data that has been unwittingly transmitted due to tools like this. If my objective was to gain the secrets of various worldwide entities, one of the first things I would do is set up seemingly innocent Pastebins, JSON checkers, online fil…

Eric here (one of the creators of JSON Hero) and this is a really good point. We built JSON Hero earlier this year and partly wanted to use it to try out Cloudflare Workers and Remix, hence the decision to store in KV and use that kind of architecture. We're keen to update JSON Hero with better local-only support for this reason, and to make it easier to self-host or run locally.