Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JSON Hero: Enhanced JSON structure visualization

jsonhero.io

Post reply on HN
Print view View original

11–20 of 203 posts

Re: JSON Hero: Enhanced JSON structure visualization

#11

Post by joeyjojo »

stevage wrote: post #9

I'm not really clear on what the value-add is here. When is one needing to "visualise" JSON in this way, without editing it? Does it really help that much? Generally I just open in VS Code, reformat and use search etc.

I could see a tool like this being really useful on my web game projects, where I would like artists/animators making contributions.

Re: JSON Hero: Enhanced JSON structure visualization

#13

Post by joeyjojo »

sorenjan wrote: post #7
kondro wrote: post #5

I like it, but don't love that it's a web app. I guess I could fork it myself, but don't particularly want to have to run a web app to browser JSON either. I wonder how easy it would be to port to Electron.

They have a VS Code extension. https://marketplace.visualstudio.com/items?itemName=JSONHero...

It just opens your json in a publicly accessible page at https://jsonhero.io/

Re: JSON Hero: Enhanced JSON structure visualization

#14

Post by throwaway0x7E6 »

stevage wrote: post #9

I'm not really clear on what the value-add is here. When is one needing to "visualise" JSON in this way, without editing it? Does it really help that much? Generally I just open in VS Code, reformat and use search etc.

to make sense of API responses

Re: JSON Hero: Enhanced JSON structure visualization

#15

Post by zarzavat »

tfsh wrote: post #8
kondro wrote: post #5

I like it, but don't love that it's a web app. I guess I could fork it myself, but don't particularly want to have to run a web app to browser JSON either. I wonder how easy it would be to port to Electron.

Forking perfectly functional browser-based web app into Electron apps is an irritating trend with very limited benefits. Some apps exist as Electron apps because they require native OS access, this app does not, therefore there is no reason to do so. Porting to Electron would be trivial but in doing so you incur the following ramifications: - the user has yet another instance of Chromium running on their device. - th…

Browsers should make it easier to interact with the command line then. I want to be able to run a command and it opens the result in a browser tab.

Re: JSON Hero: Enhanced JSON structure visualization

#16

Post by nemosaltat »

tfsh wrote: post #8
kondro wrote: post #5

I like it, but don't love that it's a web app. I guess I could fork it myself, but don't particularly want to have to run a web app to browser JSON either. I wonder how easy it would be to port to Electron.

Forking perfectly functional browser-based web app into Electron apps is an irritating trend with very limited benefits. Some apps exist as Electron apps because they require native OS access, this app does not, therefore there is no reason to do so. Porting to Electron would be trivial but in doing so you incur the following ramifications: - the user has yet another instance of Chromium running on their device. - th…

Interestingly enough, when I want the compartmentalization experience that comes from an “App” on macOS, I turn to… Microsoft Edge. Edge has a nifty little feature that lets you “Appify” a website. I mostly find this useful for company-required PWAs, and most-of-all, Microsoft Teams. The Edge-“Appified” MS Teams on macOS is leaps and bounds more performant than the “Native” (Electron) MS Teams apps on macOS (consumes ~25MB of mem vs ~800MB). Has the nice benefit of your “Apps” being a Command-Space away.

edit: clarify & format

Re: JSON Hero: Enhanced JSON structure visualization

#17

Post by bsimpson »

Hahaha - I get this when opening it in an HN browser on my phone:

    TypeError: Cannot read properties of null (reading 'getItem')
        at u (https://jsonhero.io/build/_shared/chunk-LYGVB3WT.js:1:161)
        at https://jsonhero.io/build/_shared/chunk-LYGVB3WT.js:1:407
        at Gf (https://jsonhero.io/build/_shared/chunk-PZ2Z7HGX.js:9:6560)
        at L.unstable_runWithPriority (https://jsonhero.io/build/_shared/chunk-PZ2Z7HGX.js:1:4026)
        at rn (https://jsonhero.io/build/_shared/chunk-PZ2Z7HGX.js:5:38448)
        at Xe (https://jsonhero.io/build/_shared/chunk-PZ2Z7HGX.js:9:6029)
        at yi (https://jsonhero.io/build/_shared/chunk-PZ2Z7HGX.js:7:10750)
        at https://jsonhero.io/build/_shared/chunk-PZ2Z7HGX.js:5:38670
        at L.unstable_runWithPriority (https://jsonhero.io/build/_shared/chunk-PZ2Z7HGX.js:1:4026)
        at rn (https://jsonhero.io/build/_shared/chunk-PZ2Z7HGX.js:5:38448)
Biggest SPA fail I think I've ever seen.

Re: JSON Hero: Enhanced JSON structure visualization

#19

Post by beardbandit »

stevage wrote: post #9

I'm not really clear on what the value-add is here. When is one needing to "visualise" JSON in this way, without editing it? Does it really help that much? Generally I just open in VS Code, reformat and use search etc.

I can think of one valuable use-case: parsing through JSON responses for APIs with poor fields/response documentation -- especially if you have to parse through a ton of information.

Still way more readable than XML.

Post reply on HN