Live data from Hacker News

JSON Hero: Enhanced JSON structure visualization

jsonhero.io

131–140 of 203 posts

Re: JSON Hero: Enhanced JSON structure visualization

#131
post #79

Earlier quoted context omitted.

> or a much bigger problem (if it's sensitive personal data). Personal data is a red herring. It's not the only thing that matters. For starters, using this at work with anything not explicitly public is likely a violation of your contract. In some contexts, it may even be gross misconduct or illegal and potentially exposing your employer to large fines. And, in general, I'd say a tool like this that comes without ex…

I agree, mostly. But since when isn’t it obvious that posting data with a browser will send that data somewhere? And the users here are (from what I can tell) developers . I think this is a cool tool for public data and obviously I can’t paste private data sets on any public website, ever.

> I agree, mostly. But since when isn’t it obvious that posting data with a browser will send that data somewhere?

I'd be surprised if anyone at all, specially developers, expects a browser to do anything other than transfer data to/from the internet.

Re: JSON Hero: Enhanced JSON structure visualization

#132
post #54

Earlier quoted context omitted.

It's always strange to think that we went through formats like XML (and even earlier, XDR) before inventing something as seemingly simple and obvious as JSON.

Why does React use JSX when it could be all JavaScript and JSON? My guess is that XML is good for situations where text and data is mixed.

> My guess is that XML is good for situations where text and data is mixed.

I don't agree. My take is that HTML/XML-like syntaxes benefit from familiarity from front-end developers, and a DSL to express document/component trees ends up simplifying the job of expressing document/component trees.

Re: JSON Hero: Enhanced JSON structure visualization

#134
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…

100% literally came here to make sure someone said this.

Re: JSON Hero: Enhanced JSON structure visualization

#136
post #46

Earlier quoted context omitted.

jsoncrack cannot even open the simpliest of my json files (600K: too large), whilst this handled it easily.

what is the use case for having 600K (lines? bytes?) JSON? I'm a bit shocked and curious at the same time :)

I'm converting proprietary AutoCAD DWG files to some JSON format (libredwg) I invented. 600K bytes is a very small file, with just a couple of objects.

Many other CAD formats also switched to JSON.

Re: JSON Hero: Enhanced JSON structure visualization

#137
I've been frustrated with JSON when mixing text data and content due to the default prettier/JSON.stringify/browser format, which makes it very vertical, specially when mixing in 2d/3d data/arrays. I found a simple solution was to use json-beautify[1] before printing/saving data in files. Suddenly my 2000+ lines of scroll-fast JSON became 200-300 lines of highly legible data.

[1] https://www.npmjs.com/package/json-beautify

Re: JSON Hero: Enhanced JSON structure visualization

#139

I need a JSON schema editor for macOS. I found this: https://www.json-buddy.com/ but it's Windows only and has what I call a "millions of tiny buttons" UI. JSON schema is awesome but it's really tedious to write by hand, even if the basic is auto-generated. It can also get really complex and thumbs up or down doesn't cut it for developer experience. I want something where I can debug/step through the validation.

I think nobody writes JSON Schema by hand .. I see most of them use their lang libs to generate it. What language are you using?

I agree. That's basically what I meant by, even when the base is auto-generated. In other words: you can generate a JSON schema from an example JSON. However, if you're using that to validate, say, an API response, the auto-generate tool can't possibly know what the valid range of values might be, or how some keys will shift depending on the request. Any type of variation like that requires hand-tuning.

I use it in a variety of languages: JS/TS, PHP, Java.

Re: JSON Hero: Enhanced JSON structure visualization

#140

Earlier quoted context omitted.

Ouch, this is particularly egregious: "...To opt out, set the DOTNET_CLI_TELEMETRY_OPTOUT environment variable before you install the .NET SDK"

Just to be clear: that is to opt out of the single telemetry message sent by the installer itself on successful install, not to opt out of .NET telemetry in general. You can do that at any time post install by setting the env var, no need to remove and reinstall the entire SDK just to turn off telemetry.

I still consider this fairly egregious in that if you've already installed it (but not used it) before finding this out; a bunch of details has already been reported about your environment. Does opting it before install also keep you opted out of all telemetry or does that have to be done separately?

If a new starter did this on a company machine, boom, misconduct on their first day; though I hope the network/operations team have already put a block in place for that.

That is an extreme example, but it's kind of annoying you have to look this up, and make sure you didn't typo the flag for every piece of software you use/test.

Post reply on HN