well - the point is. that we wanted to be standards compliant - and want to use existing technologies without actually reiventing a new standard or a proprietary format. (like some of the other api clients took).
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.
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!
Thank youuu !
We are open to feedback : https://github.com/VoidenHQ/feedback
This is a really interesting approach! How did you end up deciding on executable markdown as opposed to other approaches?
well - the point is. that we wanted to be standards compliant - and want to use existing technologies without actually reiventing a new standard or a proprietary format. (like some of the other api clients took).
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.
Is there a way to generate code from these specs? Perhaps via OpenAPI, Smithy, something like that?