Opened 7 weeks ago

Closed 7 weeks ago

#33791 closed New feature (needsinfo)

No Reverse Match and namespaced urls

Reported by: Malik A. Rumi Owned by: nobody
Component: Documentation Version: 4.0
Severity: Normal 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

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?

Change History (1)

comment:1 Changed 7 weeks ago by Tim Graham

Resolution: needsinfo
Severity: Release blockerNormal
Status: newclosed

It's unclear how to proceed with this ticket when you haven't made any critiques of the existing documentation on the topic. Feel free to reopen with some concrete suggestions. (Simply saying "document everything!" is not really actionable.) Thanks.

Note: See TracTickets for help on using tickets.
Back to Top