#27262: Delegate URL resolver checks to URL classes
------------------------------------+--------------------
Reporter: Sjoerd Job Postmus | Owner: nobody
Type: Uncategorized | Status: new
Component: Core (URLs) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------
As discussed in http://sjoerdjob.com/post/is-djangos-url-routing-tightly-
coupled/ and https://groups.google.com/d/msg/django-
developers/u6sQax3sjO4/t6FfSex1AwAJ, the URL checking logic is coupled to
the current implementation.
It would be better to implement a `.check()` method on the URL resolver
classes themselves, and move the logic to the relevant classes.
--
Ticket URL: <https://code.djangoproject.com/ticket/27262>
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/052.5d7345f8ae51bb60ed70e18acb98ad25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
