`curl ... > out.json` then `curl ... -d out.json`. Wrap it in a shell script for quick iterations.
> filtering through data
`curl ... | jq | grep`. I don't know of any tool that will find what I'm after faster than the shell.
For bootstrapping and quick experiments curl is right there at my fingertips, no need to spin up an electron app, make a bunch of definitions and all that. When I want something more usable OpenAPI serves as stateful and interactive test environment and documentation at the same time.
I do agree curl can get a little verbose but create an alias: `alias jc='curl -H Content-Type: application/json` and using it is as simple as `jc $URL` for GET or `jc -X POST -d '{ ... }' $URL` for the rest of the methods.
I really recommend getting comfortable in the shell, it's amazing how productive it can be and becoming a bit of a lost art these days. All the tools are composable and working together it's so zen.
`curl ... > out.json` then `curl ... -d out.json`. Wrap it in a shell script for quick iterations.
> filtering through data
`curl ... | jq | grep`. I don't know of any tool that will find what I'm after faster than the shell.
For bootstrapping and quick experiments curl is right there at my fingertips, no need to spin up an electron app, make a bunch of definitions and all that. When I want something more usable OpenAPI serves as stateful and interactive test environment and documentation at the same time.
I do agree curl can get a little verbose but create an alias: `alias jc='curl -H Content-Type: application/json` and using it is as simple as `jc $URL` for GET or `jc -X POST -d '{ ... }' $URL` for the rest of the methods.
I really recommend getting comfortable in the shell, it's amazing how productive it can be and becoming a bit of a lost art these days. All the tools are composable and working together it's so zen.