-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
fix(plugin-documentation): custom routes docgen #18142
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
Conversation
|
@Demacri Please sign the CLA. since if you don't this can't be merged by the strapi team. |
Yes, i did... i'm trying to understand why it's not recognizing it |
I can answer that question the commit was done by a none GitHub account with the name Alessandro Capezzera |
|
Thank you @Boegie19 . Email misconfig in local environment 😁 ✌️ |
|
Any chance of this being merged? It's been waiting for 6 months now... |
|
Hello @Demacri, When I try to use the collection type of If you know how to fix it, it will be great. |
Hi, it's been a while since this fix but i'll try to help you. |
|
@Boegie19 Honestly, I don't understand why some companies won't accept free labor for the products the serve to their paying customers... |
|
This pull request has been mentioned on Strapi Community Forum. There might be relevant details there: |
a7ef509 to
ce84fad
Compare
|
Important With the release of Strapi 5, we have lifted the code freeze. To ensure we can effectively review and assist with contributions, we are now only accepting PRs targeting version 5 (the develop branch). |


What does it do?
Add the ability to generate openapi paths for custom routes using @strapi/plugin-documentation.
How to test it?
Example:
src/api/myEntity/routes/my-custom-routes.ts
src/api/myEntity/routes/myEntity.ts
npm run developWithout this fix, the generated src\extensions\documentation\documentation\1.0.0\full_documentation.json will only include paths defined in src/api/myEntity/routes/myEntity.ts.
Related issue(s)/PR(s)
Fix #844 .