Was intrigued until step one of "Getting Started":
Install Node.js 20 LTS
That's gonna be a "no" from me.
Why is it a no for you ? Is Node20 problematic?
Feels weird to introduce something that’s been around for a while. I’ve been using typespec for about a year. Works well but it needs to make some leaps to match with the OpenAPI spec.
Perhaps I should see if those have been made…
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).
Was intrigued until step one of "Getting Started":
That's gonna be a "no" from me.
Why is it a no for you ? Is Node20 problematic?
Feels weird to introduce something that’s been around for a while. I’ve been using typespec for about a year. Works well but it needs to make some leaps to match with the OpenAPI spec.
Perhaps I should see if those have been made…
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).