10 comments

[ 0.18 ms ] story [ 37.5 ms ] thread
Great to see this space so active !

Building something similar : https://voiden.md

Love this.

As a literate code aligned shop, we wish more tools adopted these values for knowledge-base-adjacent tasks.

// Love OP's CLI too!

Very nice. Just did not find the spec/format for the config file.
This looks super cool, I’ve played around with making custom API clients/executers in multiple teams now and am glad to see something that I might actually use instead of re-rolling my own each time.

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…

Page currently shows

    404 This page could not be found.
I love file-based API clients. I think it’s only time to define a standard file format that all or most IDEs, editors and clients support. Fragmentation between IntelliJ, VSCode and any other tool makes the approach less useful as it could be.