3 ms·
https://www.speakeasy.com/guides/api-frameworks/typespec https://www.speakeasy.com/guides/api-frameworks/typespec This post has a bit more detail about why "we
by sixhobbits 2y ago
https://www.speakeasy.com/guides/api-frameworks/typespec https://www.speakeasy.com/guides/api-frameworks/typespec
This post has a bit more detail about why "we don't need more standards" might not be the correct take here
(Disclaimer speakeasy is a client but I wasn't directly involved in writing this and just figured it's pretty relevant here)
- lostmsu 2y agoNah, it doesn't really say why they didn't just use TypeScript.
- startupsfail 2y agoPydantic/FastAPI - it is well designed, industry proven. Doesn’t need custom DSLs.
- samier-trellis 2y agoCame here to post this. We use Django Ninja at work (basically FastAPI style endpoints for Django), and it automatically does OpenAPI and Swagger docs for us. Whatever web framework one chooses in whichver language should def have this built-in by now, IMO, seems like tablestakes for anything larger than a "micro-framework"
- lknuth 2y agoHaving your Framework generate the Docs is nice, but doesn't always fit. At work, I build backends for mobile applications. When designing new APIs to be consumed by apps, we want input from the mobile developers. We facilitate this by having an api-specs repo with TSP and using Pull Requests to discuss, track and finally commit on new APIs. It also allows mobile developers to open PRs with changes they want. The contracts are basically an interface that both sides can discuss and agree on.