-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated doc generation #809
Comments
Let me know if you want me to make a PR for this, I don't mind (Since it will make the final code more DRY) |
Thanks @PhilipWee
That sounds great. Please open the PR. |
Combining Zod, JSDoc, and some preprocessing scripts can help us autogenerate the OpenAPI spec. |
hey, any chance you could provide a process for achieving this? this is what I a researching currenty |
I would do the PoC about this sometime. However, you could combine those tools to work nicely together |
Just want to know why the PR: #812 hasn't been approve for so long? The feature he does is what I want. |
Are there any updates on this issue? Thanks! |
As far as I know, it's WIP (not ready yet). PRs always welcome anyway :) |
Describe the bug
Not really a bug, but I don't think it should be a necessity to specify the request url and request method (And perhaps even the possible responses) because all these are things that are available within the code itself
For example we can look at the folder path and exported module name and from there derive the available methods and api paths
Reproduction
/** * @Swagger * /api/hello: * get: * description: Returns the hello world * responses: * 200: * description: Hello World! */
System Info
Used Package Manager
yarn
Validations
The text was updated successfully, but these errors were encountered: