-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add Nested Routes Support and Documentation #20
Comments
I tried addressing this. After short research I thought that something like this would work out of the box:
It turns out, that while the route gets properly built, the path params are not resolved dynamically as integers (they are parsed as raw path strings). Only default id gets recognized as a path param. I can see they are all gettin passed in
but not sure what magic makes the (note I have one more layer of |
I'll take a proper look at it later today |
Sorry, had a really long day. I'll try to do it on friday |
I have tested that even further. Turns out it's just swagger docs not fully recognizing the nesting, but the API works flawlessly out of the box!!!
UPDATE: passing |
That's great! |
Describe the bug or question
Handling something like this scenario:
The text was updated successfully, but these errors were encountered: