-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request -- trigger for JSON editor #138
Comments
Good suggestion, thanks. It would have to be a single trigger for only the outermost/root JSON editor, right? |
That's my use case.
…On Wed, Dec 18, 2024, 3:20 PM Carl Smith ***@***.***> wrote:
Good suggestion, thanks. It would have to be a single trigger for only the
outermost/root JSON editor, right?
—
Reply to this email directly, view it on GitHub
<#138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVCNM643JDQSI2PRM2VDAT2GHKKFAVCNFSM6AAAAABT3L3CWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGE4TKMZQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Would need to do something like this: Just putting that here as a note to self. There's been another request for an external trigger for something else (can't remember what right now), so I'll probably do this with a range of internal functions that can be triggered via a single prop. |
Hi @tony-gutierrez -- I've implemented this functionality in the latest beta if you'd like to try it out: https://www.npmjs.com/package/json-edit-react/v/1.25.0-beta1 See the documentation for "External control". Let me know if you have any feedback before I make an official release (non-beta). |
A common use case is probably to initially paste in a chunk of json, and then edit it in the editor.
There is an edit button next to root that goes to a nice textarea for pasting in JSON. I would like to be able to trigger that view externally with my own button.
Currently I workaround by using tabs, one with the editor and one with my own textarea.
The text was updated successfully, but these errors were encountered: