You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But for starters (and existing project with a lot of routes) it would be great to generate a spec simply based on standard Next.js route.ts handlers and JSDoc. It would be really cool.
I checked Route Handler as well, looks pretty useful. But migration would take a lot of time and I need a quicker solution for now over my plain Next.js app codepase to at least list all API endpoints (and use some data from JSDoc if possible).
Does it make sense?
The text was updated successfully, but these errors were encountered:
Yea, I hear you. You've got a point. When I was migrating for myself, I've done that manually and it was a real pain. I think I can make a route generator from a swagger.json but not JSdoc. I'm really done with JSdoc after that migration.
@dmythro take a look at https://github.com/jellydn/next-swagger-doc. It might be closer to what you're looking for. Note that you will need to use @openapi tags to add the endpoint spec in a way that looks like a open api yaml file.
@dmythro take a look at https://github.com/jellydn/next-swagger-doc. It might be closer to what you're looking for. Note that you will need to use @openapi tags to add the endpoint spec in a way that looks like a open api yaml file.
Thanks! I did check that before and not really a solution I'd look at. Mainly, it doesn't really utilise app routing and you have to specify routes manually for each request handler. Plus, this @swagger thing is required. And for existing project with a lot of APIs is exhausting to migrate to.
Hi. Found this, looks cool.
But for starters (and existing project with a lot of routes) it would be great to generate a spec simply based on standard Next.js
route.ts
handlers and JSDoc. It would be really cool.I checked Route Handler as well, looks pretty useful. But migration would take a lot of time and I need a quicker solution for now over my plain Next.js app codepase to at least list all API endpoints (and use some data from JSDoc if possible).
Does it make sense?
The text was updated successfully, but these errors were encountered: