-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
APIController cannot register on router #163
Comments
@zhoujingryan this is not supported at the moment |
Also checkout this out #162 if that helps |
It'd make a lot of sense to be able to register them on routers as well as the base api. There is a Router class in ninja_extra after all, and you can use it like a regular ninja router, but you can only attach normal function based views to it and not the ninja_extra controllers. The workaround for me is to use the desired full path in the controller definition. But of course if I change the routers I have to manually edit those paths as well. |
I will look into this. Sorry for late response @MisaoDev |
APIController cannot register on router.
is this behavior intentional?
user can only register their apps api controllers on the root api instance.
but we often have a common app route on every app imo.
now:
prefer:
The text was updated successfully, but these errors were encountered: