top | item 46360571

(no title)

jamiepond | 2 months ago

This is a really interesting approach! How did you end up deciding on executable markdown as opposed to other approaches?

discuss

order

dhruv3006|2 months ago

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.

gregopet|2 months ago

Is there a way to generate code from these specs? Perhaps via OpenAPI, Smithy, something like that?