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).

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 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.

Have to agree that this update has felt pretty jarring when I’ve been used to how the app has been working. It felt like Apollo before but now it feels like Apollo’s little annoying shitty brother. I remain hopeful that the changes will be sorted out but we will see.

Edit: spelling error

My favorite of the year so far. My nostalgia was off the charts and I loved every second of it.