Re: [Django] #36585: Add `DateConverter` for path resolving (was: Add `DateConveter` for path resolving)

[Django]

#36585: Add `DateConverter` for path resolving
-------------------------------------+-------------------------------------
Reporter: Y3K | Owner: Y3K
Type: New feature | Status: assigned
Component: Core (URLs) | Version: 5.2
Severity: Normal | Resolution:
Keywords: | Triage Stage:
url,path,converter,date,isoformat | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Y3K):

* summary: Add `DateConveter` for path resolving => Add `DateConverter`
for path resolving


Old description:

> (I searched for `Converter` on both tickets and feature submissions,
> didn't get any meaninful results.)
>
> I believe there is value on having a built in `DateConveter` that follows
> ISO8601 format for path.
>
> The [https://docs.djangoproject.com/en/5.2/topics/http/urls/#example code
> example] that Django currently has in the docs does not produce ISO
> compatible date paths (i.e. month and day are not zero-padded).

New description:

(I searched for `Converter` on both tickets and feature submissions,
didn't get any meaninful results.)

I believe there is value on having a built in `DateConverter` that follows
ISO8601 format for path.

The [https://docs.djangoproject.com/en/5.2/topics/http/urls/#example code
example] that Django currently has in the docs does not produce ISO
compatible date paths (i.e. month and day are not zero-padded).

--
--
Ticket URL: <https://code.djangoproject.com/ticket/36585#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.