Regenerate the codebase using swagger 2026-05-07#320
Conversation
|
Hey @alhumaw — good to see the client.ts automation finally landing. That TODO has been there for a minute and we already have a live sync bug on main where ServerlessExportsApi is in apis/index.ts but missing from client.ts. So yeah, this is overdue. Few things before merging:
On the PR scope - I get why the tooling and regen are bundled (markers need to exist for the script to work), but 20k lines of generated code makes the interesting part invisible — GitHub can't even render this diff. If you could split it (tooling + markers first on the existing API list, then regen as a follow-up). Not blocking on this though, just a preference. Minor note...since Node is already a hard requirement for this repo, a 30-line .mjs script would avoid adding Python as a build dependency. Not a dealbreaker. Let me know what you think |
|
Fantastic feedback @carlosmmatos. Made the changes, here's a summary:
Shared end marker: updated to paired unique markers ( Error handling: script now exits with a clear message if any marker is missing, and prints On splitting the PR: Agreed. Will handle future PRs differently if not blocking.
|
New API Services
Tooling