6 ms·
So, this is an idea I've been scratching at during the holiday week. It's my first project in Go, so be gentle. The code hasn't quite caught up with the documen
by twodave 5y ago
So, this is an idea I've been scratching at during the holiday week. It's my first project in Go, so be gentle. The code hasn't quite caught up with the documentation, but I think I'm far enough where I'd like some feedback.
This project is an attempt to remove Postman as a dependency from my general workflows for testing HTTP APIs. The project name was chosen because it's short and a synonym for REST. I believe this sort of tool should:
- be free (MIT license)
- be file-based so work can be committed to Git
- easy to work with (at least for developers, via YAML and eventually some light scripting support)
- be able to run headless as part of a CI/CD workflow
No cloud cruft. No subscription model. No telemetry. No ads. Zero infrastructure. Maybe if I get enough interest I'll build a UI and sell that, but the core CLI should always be free.
I've got an idea how I'll be adding scripting support (probably javascript, via the Otto package).
Here's the ask--does this project make sense? Should I keep going with it? Is something REALLY BIG missing that I haven't mentioned?
Obviously I've thrown this together in about 10-15 hours--there's plenty of room for growth/refinement. Still, I think it fills a need. Worst case I'll be using the tool myself, but I want to know just how useful it is. Thanks in advance!