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…
There isn’t anything interesting here.
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…
If my spouse were to ask for me to do that, that would be an actual discussion in which I would seriously consider it. My partner has not asked me for such a request so I don’t consider it.
This was never something that came up as a child and I didn’t share a room in my teenage years.
Well, shit. I have this. It actually sucks.
From just this year, I can recall:
I can’t sleep next to anyone who doesn’t know about the condition and consents to the possibility of having to wake me to stop it. It caused friction in my early marriage (no other serious gfs) but once my spouse helped me realize what I was doing did i understand this occurred.
If kids are around, probably Howl’s Moving Castle or another Studio Ghibli movie.
If I am gearing for adults, a comedy like Chef where the premise is lighthearted but not a total snooze fest.
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).