Opened 14 years ago
Closed 14 years ago
#14926 closed (invalid)
Support nesting app namespaces with current_app
| Reported by: | David Cramer | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.2 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
URL resolution should allow nested app namespaces with simple resolution:
reverse('admin:index', current_app='nested:admin')
Right now this isnt possible as the populate method on the resolver doesnt handle recursion. However, explicitly calling applications does work:
reverse('nested:admin:index')
Note:
See TracTickets
for help on using tickets.
I'm not sure I follow the advantage here. current_app isn't being provided as a prefix; it's context in which the URL name should be interpreted. For example, there can be multiple admin app namespaces deployed; current_app is used to define which instance of the admin app should be used.
Closing invalid; there isn't enough detail here to establish the API or functionality that is being requested.