#30515: Document django.shortcuts.resolve_url.
-------------------------------------+-------------------------------------
     Reporter:  sage                 |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Documentation        |                  Version:  master
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Eeek. This goes back ''some way''.
 [https://code.djangoproject.com/ticket/15552#comment:9 From #15552]:

 > I placed it in utils because I wasn't sure you'd want resolve_url as
 part of the "public" shortcuts module.
 > But if that is ok I'll update the patch.

 To which Jannis replied:

 > Yeah, that's fine.

 "Yes that's fine, it can be part of the public API" vs "Yes, that's fine
 to put it there, but we'll leave it private"? — Not sure.

 Either way it was never documented.

 I can see a use-case: wanting the URL for a `get_context_data()` maybe
 (but I can't remember ever using this myself: I'd be inclined to want to
 know if I had a model or a view name and a URL at the call site; by the
 time I don't know that I've discovered `resolve_url()` anyhow.)

 _Meh_...

 Closing in line with TicketClosingReasons/DontReopenTickets. Happy to look
 at a patch and/or discuss on django-developers but... 🤷‍♀️

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30515#comment:5>
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/067.5e0cfb4b1ed1a52bd9533e357f79209a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to