Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
Over last few years, we've been hard at work on https://typespec.io/, a modern API definition language. This language is designed to meet the evolving needs of API developers, architects, and managers in an environment where the delivery of consistently high-quality APIs and related experiences is becoming increasingly complex and critical.
As an FYI to myself: the leaps have not been made.
I would love to have TypeSpec enable support for examples, callbacks, and links. If it added those three, it’d be a total game changer (for me).
My position is one of always design an API first (produce the OpenAPI document of what you want to build) and get buy off from your customers/stakeholders. Then when we start coding, we know exactly what well the end result should be.
Even better would have the ability to do request/response validation via a OpenAPI spec in .NET. Still holding out on that pipe dream (I know it’s available via other languages).
As an FYI to myself: the leaps have not been made.
I would love to have TypeSpec enable support for examples, callbacks, and links. If it added those three, it’d be a total game changer (for me).
My position is one of always design an API first (produce the OpenAPI document of what you want to build) and get buy off from your customers/stakeholders. Then when we start coding, we know exactly what well the end result should be.
Even better would have the ability to do request/response validation via a OpenAPI spec in .NET. Still holding out on that pipe dream (I know it’s available via other languages).