-
Notifications
You must be signed in to change notification settings - Fork 438
fix list views with parameters in last path segment not named "list" views #917
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
fix list views with parameters in last path segment not named "list" views #917
Conversation
d664f9d
to
e2707c5
Compare
e2707c5
to
e0a649d
Compare
Thanks for digging into this @terencehonles, looks really good. I'd like to have a unit test for this to validate the behaviour when there is and isn't a detail attribute before we merge. Could we also move the |
e0a649d
to
0d6e382
Compare
Isn't this what the reference schema is testing? I effectively fixed the test with https://github.com/axnsan12/drf-yasg/pull/917/files#diff-741bf237457101c6d297e385e111f8b5477fbbd9369c53a05c08c64e307d0e17 See:
The detail attribute comes from the viewset handling, and this is a view class.
Done |
0d6e382
to
984d59f
Compare
@JoelLefkowitz I updated this to include the commit that fixed the CI |
Thanks for looking at the other PR and merging in |
…views This fixes the auto generated operation keys and operation ID. For list views which have a parameter in their last path segment.
6e80809
to
0398e87
Compare
Looks all good, thanks @terencehonles 🥳 |
This fixes the auto generated operation keys and operation ID. For list views which have a parameter in their last path segment.