CarlosNZ
Any plans on making a viewer-only?
Thanks for your work on this tool, it's a pretty JSON renderer.
I need a viewer, not an editor. I'm currently passing restrict* props to false, which works. But I was wondering whether a viewer-only component (e.g. import { JsonViewer } from "json-edit-react";) would help trim the size of my final bundle. Thoughts?
Hey, thanks for your comments.
I hadn't really planned to do that. I'd be happy to export a different "Viewer" component, but that would just be a wrapper around the main component with preset props. So I don't think that would help with bundle size at all, since I wouldn't be making a separate codebase for it (and don't really have any desire to, to be honest).
If you are looking for viewer-only, check this
https://www.npmjs.com/package/react-json-tree
If you are looking for
viewer-only, check this https://www.npmjs.com/package/react-json-tree
I'll take a look, thanks. But is it as pretty as this one though? :)
The lib react-json-tree is slightly larger according to bundlephobia.
https://bundlephobia.com/package/[email protected] https://bundlephobia.com/package/[email protected]
But I suppose the real test should be looking at the size of the lib after tree-shaking.
How about just a single viewer prop, which would disable all editing capability, so syntax would be:
<JsonEditor data={myData} viewer />
It wouldn't really help with the bundle size though, as it wouldn't be a separate code base, it would just be a shorthand for manually adding all the disable editing props. Just wondering if people would find that useful, or if they're happy to just include the disable editing props?
I think it's okay to leave it as is. I might fork the repo when I get a chance and experiment by ripping out the editing features and see how small we can get...
I think it's okay to leave it as is. I might fork the repo when I get a chance and experiment by ripping out the editing features and see how small we can get...
It would be great if you could share it here too