yapi.run
https://github.com/jamierpond/yapi
Still very early, but it makes me much more productive vs Postman, Bruno, Insomnia, etc.
If youre a nvim/tmux culture human, you might like this!
One thing I’ve previously found very useful is the ability to select multiple ‘environments’ at once (I’ve previously split this in to e.g. environment+session or environment+user before). The ability to merge a set of variables together lets you define variables for _where_ I’m calling (local, staging, etc), but also who/what I’m calling (specific users, types of profiles/packages (how does this api behave if I switch between a free vs paid licence), etc).
Also echoing another comment, the blog linked gives me a 404 page now. Additionally, the GitHub for this projects seems have a ton of blank issues saying “help yapi made me too productive”? Rather odd, I probably won’t be running this project directly anytime soon…
Building something similar : https://voiden.md
and moreover we had this fundamental idea that documentation and testing should be in a single source of truth to avoid documentation drift (not just the spec drift).
And hence we came up with the idea of using markdown as the baseline and doing everything around it.
We have it in beta now : https://voiden.md/download (Only Linux and Mac)
And in the future we also plan to support graphQL but not smithy for now.
Also, while a nice API document is a godsend (and sadly often missing in practice), a way to generate the consuming side of the API (again via various mechanisms) is also a very useful thing.
Re-reading the page, perhaps I got it wrong and it works the other way around? Voiden uses e.g. OpenAPI files and verifies it's still compliant with them? That would work, although it's a bit of a double effort.. still, useful in many cases.
As a literate code aligned shop, we wish more tools adopted these values for knowledge-base-adjacent tasks.
// Love OP's CLI too!
We are open to feedback : https://github.com/VoidenHQ/feedback
404 This page could not be found.