#35403: URL path with optional parameter
-------------------------------------+-------------------------------------
Reporter: Patrick Hintermayer | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 5.0
Severity: Normal | Resolution: invalid
Keywords: url | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => invalid
* status: new => closed
Comment:
Hi Patrick 👋 I think this ticket is a bit of a mix of a support request,
new feature request, and docs update request.
With support requests (how do I best achieve X with Django), I recommend
asking in the [https://forum.djangoproject.com/c/users/6 forum] because
you will have many more people who can help answer.
I think I would have either gone for solution 2 using a default for
activation_token (a bit like
[https://docs.djangoproject.com/en/5.0/topics/http/urls/#specifying-
defaults-for-view-arguments what is documented here]) or used a query
string like `activate/?token=some-activation-token` and then I can access
token in the [https://docs.djangoproject.com/en/5.0/ref/request-
response/#django.http.QueryDict QueryDict]
([https://docs.djangoproject.com/en/5.0/topics/pagination/#using-
paginator-in-a-view-function example involving pagination]).
I believe we have this functionality already and so something like
`"/<int:some_id?>/"` would not be required.
Before we can discuss a docs update, you need to know what you would have
wanted to see. So I would encourage that you discuss this topic on the
[https://forum.djangoproject.com/c/users/6 forum], agree on an approach,
and then decide if the docs are clear enough or if there is an enhancement
available.
--
Ticket URL: <https://code.djangoproject.com/ticket/35403#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f140177fc-ab0332e6-d72c-4645-bf58-0f6d6da47ee2-000000%40eu-central-1.amazonses.com.
