#16774: Backtracking URL resolver
-------------------------------+--------------------------------------
Reporter: Nowell Strite | Owner: Tijani-Dia
Type: New feature | Status: assigned
Component: Core (URLs) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Adam Johnson):
Well done for reviving an old ticket Tijani-Dia
I think I'm against this feature. It won't interact work with
Middleware.process_view() particularly well at all. For example, atomic
requests, as [https://groups.google.com/g/django-
developers/c/UQZmLNzlDcw/m/8NfZxMOMEQAJ Florian mentioned on django-
developers], or `@csrf_exempt`.
Also there's a potential footgun: if a view raises `DoesNotResolve` at a
very late stage, the view could have had many side effects but then be
less visible in logging or APM traces.
I think the already-suggested solution of one view that calls other
subviews is sensible for most situations.
--
Ticket URL: <https://code.djangoproject.com/ticket/16774#comment:27>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.b31ca78624c260681a7d548de348deb2%40djangoproject.com.
