#22737: Ability to implicitly preappend current_app to reverse URL resolution.
-----------------------------+--------------------
Reporter: CVi | Owner: nobody
Type: New feature | Status: new
Component: Core (URLs) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
I want to be able to implicitly preappend the current_app as a namespace
to some URL reverse-resolutions.
My suggestion would be that names starting with a colon ':' (e.g. empty
string as first level namespace) implies current_app if present.
A very simple 2-line solution can be found
[https://github.com/CVi/django/commit/c501c522edebec5fc4d2312c6ec8f7a50fa8ddcd
on my github page]
The question is if this breaches any philosophies of Django. There's no
reason for me to create an elaborate patch including additional tests for
this, if it's going to be cut down for political/design reasons. Therefore
I am not ticking "has patch" just yet.
The possible use-cases for this is template reuse and making applications
modular by simply splitting them up. (my use case covers both)
--
Ticket URL: <https://code.djangoproject.com/ticket/22737>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/046.eb131a254d931d454c6e69d7dc16e0f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
