#33791: No Reverse Match and namespaced urls
-------------------------------------------+------------------------
               Reporter:  Malik A. Rumi    |          Owner:  nobody
                   Type:  New feature      |         Status:  new
              Component:  Documentation    |        Version:  4.0
               Severity:  Release blocker  |       Keywords:
           Triage Stage:  Unreviewed       |      Has patch:  0
    Needs documentation:  0                |    Needs tests:  0
Patch needs improvement:  0                |  Easy pickings:  0
                  UI/UX:  0                |
-------------------------------------------+------------------------
 There have been a lot of changes in the url syntax over the years, and I
 am confused as to what the current syntax is supposed to be. For example,
 I
 distinctly recall that at one point we were to use the 'app:instance'
 syntax in get_absolute_url(), but I see no reference to that in the
 "https://docs.djangoproject.com/en/4.0/ref/models/instances/#get-absolute-
 url" docs for get_absolute_url().

 I did find it on Stack Overflow,
 "https://stackoverflow.com/questions/9026024/django-get-absolute-url-and-
 named-url-with-namespace" here.
 Now although that question and answer are from 2012, note the comments
 from 2016 and 2020 ''asking the **same** questions!!!.''

 By the same token, the namespace kwargs has also changed dramatically,
 from a straight namespace = myapp to a 2-tuple where the app name, but not
 "namespace = " is used instead.

 Clearly, we are confused, because these changes are **both** too frequent
 **and** too subtle for us to keep up with.

 Here is my feature request: A single, clean, and comprehensive explanation
 in the docs that covers the relation between NoReverseMatch,
 get_absolute_url(), namespaced urls, named urls, and God knows what else -
 ''on the same page'', or ''in the same document''  would be **extremely**
 helpful, at least to those of us who are not working with Django every day
 of our lives.

 This may be a pointless aside, but what reasonable software development
 philosophy undergirds all these frequent changes in the first place? In
 other words, ''Why isn't the Django interface more stable?''

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33791>
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/010701817e2516a5-8441bc87-67b4-4b36-a10c-532b661ea2f3-000000%40eu-central-1.amazonses.com.

Reply via email to