Skip to content

[PMM-630]: Update TypeSpec Guide#93

Open
philsturgeon wants to merge 6 commits intospeakeasy-api:mainfrom
philsturgeon:guide/typespec
Open

[PMM-630]: Update TypeSpec Guide#93
philsturgeon wants to merge 6 commits intospeakeasy-api:mainfrom
philsturgeon:guide/typespec

Conversation

@philsturgeon
Copy link
Contributor

@philsturgeon philsturgeon commented Dec 30, 2025

TypeSpec has matured a lot since this was written for 0.58, it's on 1.7.0 now and supports OpenAPI v3.2, so lets update all our examples and talk about the future.

Please merge sample code: speakeasy-api/examples#40

Please delete this old repo: https://github.com/speakeasy-api/typespec-openapi-example

@philsturgeon philsturgeon requested a review from a team as a code owner December 30, 2025 17:35
@github-actions
Copy link

github-actions bot commented Dec 30, 2025

🔗 Preview your changes
https://speakeasy-b1jenle8f-speakeasyapi.vercel.app
(The preview may still be building. Check back at this link in a few minutes.)

@philsturgeon
Copy link
Contributor Author

philsturgeon commented Dec 30, 2025

@ndimares ready for January.

Copy link

@baywet baywet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, I gave it a high level review. Beyond the ad-hoc comments, it might be worth expanding two aspects:

  • Why would anyone choose to get SDKs generated from Speakeasy vs TypeSpec since this is a new possibility from adopting TypeSpec?
  • An important benefit from using TypeSpec is to enable the use of linting rules directly in the contract tooling (no 3rd party required). That improves the API consistency and quality, which in turns improves the quality of SDKs (however they end up being generated).

@philsturgeon philsturgeon marked this pull request as draft January 9, 2026 17:59
@philsturgeon philsturgeon marked this pull request as ready for review February 25, 2026 13:35
@philsturgeon
Copy link
Contributor Author

@ndimares ready to merge along with its sample code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants