this post was submitted on 29 Apr 2024
28 points (93.8% liked)

Programming

17326 readers
234 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
top 4 comments
sorted by: hot top controversial new old
[–] JakenVeina@lemm.ee 15 points 6 months ago (1 children)

Was intrigued until step one of "Getting Started":

Install Node.js 20 LTS

That's gonna be a "no" from me.

[–] hector@sh.itjust.works 5 points 6 months ago

Why is it a no for you ? Is Node20 problematic?

[–] jackal@infosec.pub 9 points 6 months ago (1 children)

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…

[–] jackal@infosec.pub 1 points 6 months ago

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