Show HN: I made a tool to easily transform and manipulate your JSON data (jsontransformer.com)
Hey NN,
I've create a tool that allows you to easily manipulate and transform json data. After looking round for something to allow me to perform json to json transformations I couldn't find any easy to use tools or libraries that offered this sort of functionality without requiring learning obscure syntax adding unnecessary complexity to my work or the alternative being manual changes often resulting in lots of errors or bugs. This is why I built JSON Transformer in the hope it will make these sort of tasks as simple as they should be.
Would love to get your thoughts and feedback you have and what sort of additional functionality you would like to see incorporated
Thanks! :)
https://www.jsontransformer.com/ (Link in case the other url doesn’t work)
22 comments
[ 3.7 ms ] story [ 61.7 ms ] threadBetter to put the effort into learning jq.
Here's a screenshot of my own efforts so far: https://github.com/user-attachments/assets/6fac23c3-79ef-4c0...
It's not a service I could see wanting to pay more than just a tip for it existing. A sometimes useful VSCode extension is probably the extent of the usefulness.
Flippant HN comment aside, the syntax for trivial manipulations in jq is pretty straightforward, very similar to defining a dictionary in python. Non-trivial transformations are going to be complex regardless and not having to learn an 'obscure syntax' isn't going to make it easier to get your head around.
It reminds me of when people release a "friendlier syntax" for regular expressions: at the end of the day you still have to learn the underlying concepts in order to complete your task.
In order to use your tool it looks like you still need to learn JSONpaths as a concept and then learn what all the operators in your drop downs mean at which point why not learn some obscure syntax?
And then I have the overhead of an electron app which I'm paying $9 a month for.
Maybe this has a future as the component of someone else's all-in-one low/no-code ETL platform, but as a standalone tool being pitched to the HN crowd it makes no sense.
Is it worth $9/mo. to anybody? Not sure, but if your entire day is spent wrangling with JSON data ... maybe?
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!