-
Notifications
You must be signed in to change notification settings - Fork 481
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
[discussion]: allow swagger-scanner deepScanRoutes to be recursive or go down an extra level #3102
Comments
Ideally I would like to implement this so as to benefit the team I am working with, but I also recognise that this would be my first contribution to the nestjs repo so I appreciate any feedback/ suggestions/ improvements. Thank you! |
Would you like to create a PR for this issue? |
Yes, I will submit it next week. Anything to note? |
Any update ? |
Still working on it! Will submit a PR in a few days hopefully 🙏 |
I made PR to this issue. |
Aw dang was still working on mine, but since I couldnt get it to work probably would be better to go with yours! Had a question if anybody here could help me out answering it - this was my updated code for denormalized paths,
|
If I understand correctly, does this mean that all routes are scanned even when |
Ah I see, that's interesting, thanks for explaining where i went wrong |
Let's track this here #3186 |
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
Swagger scanner does not support going more than one level down (with the deepScanRoutes option), and I would like for there to be an additional flag/ parameter that would allow it to scan 2 levels down, or recursively if possible.
Describe the solution you'd like
I would like to implement a recursiveScan flag that would allow Swagger to scan more than one level down, in the case of such consolidated apps. If this is against design decision, perhaps I would adapt the deepScan to accept a parameter of 1 (default) or 2, scanning an extra level down. This change would be implemented entirely in swagger-scanner.ts.
Teachability, documentation, adoption, migration strategy
I will adapt any existing swagger-scanner documentation and update it for this new change.
What is the motivation / use case for changing the behavior?
Swagger was a functional choice when we operated several microservices, as we only needed to deepScan one level down. Recently we have consolidated several microservices into an app, and as a result we need to scan an additional level down, which swagger does not currently support. To comply with the single level deepScan would require shifting all the routes up one level which would mess up the way the app is configured as a consolidation of sub-apps.
The text was updated successfully, but these errors were encountered: