6 ms·
This is such a cool tool! I wonder if the developer audience might me a bit of a misfit when we have stuff like jq or duckdb. But here's a use case I had a few
by _benj 2y ago
This is such a cool tool! I wonder if the developer audience might me a bit of a misfit when we have stuff like jq or duckdb.
But here's a use case I had a few years ago. I was working with this system that needed occasional calibration from time to time from non-developers (read Product Manager or Technicians). The calibrations were stored in JSON, but JSON is quite finicky regarding syntax, specially when edited manually.
I implemented a graphical structured JSON editor that would take a JSON file, present you input fields to edit the JSON (input for text, checkboxes for bools, etc) and would allow the user to edit the JSON graphically and produce a valid JSON at the other end.
It was the tool I wish I had to tell the technicians to use when they needed to update things on the JSON file without manually editing the file.
I never published the project but it was really fun to work on it because I needed to handle the JSON in order, use types, and such things that JSON doesn't support so I ended up using Pest.rs, directly editing the AST, compiling to WASM... first time I using PEGs and such.
Best of luck with your project!
- sonnyburni 2y agoThanks so much for the feedback and sharing your experience - really appreciate it :) TBH my target audience was more non technical/ less technically proficient/ developer adjacent people who might have to interact with json data and need to perform these sort of updates so great to hear you had a similar use case in the past? In your opinion what sort of things would need to be added/changed to make this more appealing to that audience based on your experience in the past?