getting started with typespec

typespec is a new language for designing your API specifications upfront programmatically. typespec is a typescript style language that dramatically simplifies designing api's through support of inheritance, templates, interfaces and operations. using typespec you can take your simple api model design and generate openspec api 3.0 (swagger) definitions from it. In the future i see this being a key tool for generative ai to generate api's also.
In this video chris walkthrough how to get started with typespec and why its important.

[@_marioguerra_]

Great video! I'm the PM for TypeSpec at MS, from the comments it looks like there is interest in back-end code generation from TypeSpec, which we're currently working on.

[@_marioguerra_]

PS - what software are you using to do the opaque code overlays on your video?

[@chrishayuk]

Awesome job with TypeSpec Mario, big fan of where it’s going. Looking forward to seeing backend code generation.

[@chrishayuk]

As for the effect. It’s the screen record with opacity that creates the overlay effect. However it’s really how I light the room, set the lumetri on the cam record and screen record that allows me to achieve the effect

[@JohnMcclaned]

Awesome video. The question is now how to use the typespec to implement typesafe apis in typescript without having to rewrite the spec in typescript

[@chrishayuk]

I sort of agree that generating typescript boilerplate is a next logical step for this

[@johntdavies]

Chris, I really enjoyed the video thanks. My world is C/C++ and Java and recently Python. I managed for follow the video well but was lucky I had the node stuff installed on my laptop. What would be interesting to me is how to now implement a simple back-end service in Python (or Java) that exposes the APIs you have defined and something simple (out of my knowledge base) on the front-end to interact with the API. My suggestion would be something like a very simple chat-response from a local LLM.

[@chrishayuk]

I really like that idea

[@everyhandletaken]

Having written spec manually in order to use with Swagger, I can see that it is a pain to do, but I did so in JSON to avoid YAML & I think that is a lot easier (why do we need YAML, when TOML exists.. but anyway) If this could then create the routes for me, it would be a significant benefit, but otherwise I am learning all those decorators, various imports, namespaces and using statements, having to compile for each change etc, when I could have just written myself manually, right.. Good video, even if I'm not convinced on it ☺️

[@chrishayuk]

I kinda went through this thought process myself but then landed back onto the up front design and ability to design schemas across services. If you’re doing a couple of services I could agree but if looking at a complex estate, I’d argue that it doesn’t get modelled and why this works as an approach. But I totally get your view as I was there with the same view originally

[@everyhandletaken]

@@chrishayuk that makes sense too. I will give it some more thought. Thanks Chris!

[@sorryforwhat416]

Hello Chris! Do you have an idea what i need to do in VSC to see the real time Swagger on the side interface? Saw this a lot of times but don't know how to do it

[@chrishayuk]

In the video, I just do the compile and then open up the file, that’s all you need to do