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
Router registry is not working as expected #292
Comments
Hi, @mcosti. Thanks for reporting it as an issue. Yeah. I agree with you that would be better to not need to add the Yet I could not figure out a clean way to do it after poking around DRF sourcecode for a while. |
Hey @alanjds . Could you maybe share what you tried and it didn't work? Thanks |
This is a desirable improvement, would love to contribute if I can. Have either of you made headway on this? |
I personally haven't, I just used the hack above in my project |
Hey, thanks for this nice package!
In our code we use this pattern:
The problem while using this package is that nested_router.registry does not contain the parent resource in the name, so the API will end up being
/api/v1/nameservers
instead of
/api/v1/domain/<domain_pk>/nameservers
My hack-ish solution is this one:
But I would very much prefer if I could avoid this.
Thanks!
The text was updated successfully, but these errors were encountered: