Love TypeSpec, agree it makes writing OpenAPI really easy.
replyBut I’ve moved to using https://aep.dev style APIs as much as possible (sometimes written with TypeSpec), because the consistency allows you to use prebaked aepcli or very easily write your own since everything behaves like know “resources” with a consistent pattern.
Also Terraform works out of the box, with no needing to write a provider.
Which parts of Openapi does it fix?
replyLooking at the first example - it's far less verbose. Although, seems to be suspiciously minimal, so I can't even tell from a single .tsp route definition what response content type to expect (application/json is the default most likely).
replyI would guess that is defined by the `@route` decorator.
replyIt’s actually human-readable, it has generics, it supports sum and product types in a much more natural way. There’s a lot more, that’s just off the top of my head.
replyOpen api is an exchange format, it quickly become to verbose and repetitive, it is only OK when auto generated and consumed by tooling.
reply