;)
[1] https://github.com/atom/atom/issues/8864 [2] https://github.com/atom/atom/issues/979
21–30 of 60 posts
;)
[1] https://github.com/atom/atom/issues/8864 [2] https://github.com/atom/atom/issues/979
There's addons/extension for Chrome and Firefox. Both also called JSON Viewer (different author). For really large files I use a command-line tool plus grep and awk though https://stedolan.github.io/jq/
jq looks promising but I still need to view the JSON file first. I want to be able to somehow get the general understanding of the structure very quickly and interactively. The tree control works very well for that. JSON Viewer is almost perfect but it doesn't work with local files.
It's super handy. Drag and drop json files into a new tab.
Link: https://chrome.google.com/webstore/detail/json-formatter/bcj...
If you're familiar with vim, you can do this cat unformatted.json | python -mjson.tool | vim - And then use vim's folding methods to navigate the file ( http://vim.wikia.com/wiki/Folding )
There's addons/extension for Chrome and Firefox. Both also called JSON Viewer (different author). For really large files I use a command-line tool plus grep and awk though https://stedolan.github.io/jq/
jq looks promising but I still need to view the JSON file first. I want to be able to somehow get the general understanding of the structure very quickly and interactively. The tree control works very well for that. JSON Viewer is almost perfect but it doesn't work with local files.
I view them unfavorably.
It is really important to chop up your JSON files into smaller sub-files. This will not only make it easier to backup and read manually but will usually give you a speed boost (can read to and write to more then 1 part of the "db" at a time).
I view them unfavorably.