-
Notifications
You must be signed in to change notification settings - Fork 463
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
Documentation not working when same name of controllers reside in scopes #455
Comments
Same here. I have 2 routes: , and apipie only shows one. I found this closed issue from 2013: #104 Any idea? |
+1 |
I've found the solution - actually the library supports it, but you have to opt-in in this behavior (for whatever reason). See https://github.com/Apipie/apipie-rails#configuration-reference - the configuration parameter
Even after you do this, the names of api resources will be ugly ( |
@yr0 it works ;) |
Before the ugly names addressed, monkey patching can save our eyes:
|
This doesn't appear to work with response validation, i.e.
|
I have 2 controllers having the same name but in different scopes and have the different routes but documentation not considering both , its considering only one , please look at the following example
courier devices controller
user devices controller
on documentation I see only couriers part like the following
I dont see my users url documentation, Whats wrong in that ? is this gem not working for scopes?
The text was updated successfully, but these errors were encountered: