OpenAPI Codegen #1103
Draft
OpenAPI Codegen #1103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
why not, but not really a priority, i personally never use openapi and wasted so much time trying to make SDKs in the past with it which was not worthwhile (even in bigtech teams, we gave up on it, too hard to maintain) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is WIP PR to codegen OpenAPI routes for type safe API calls, significantly improving code quality, reducing bugs and speeding up development time.
Navigate to this URL to download the spec file.
http://127.0.0.1:3030/openapi.jsonThis can now be used to generate type safe API client in any language.
Todo
@screenpipe/apifor developers?Demo:
a.mp4