DateDetailView should accept less specific dates, ie Year/Month or just Year
|Reported by:||AndrewIngram||Owned by:||Moon Limb|
|Cc:||andy@…, hirokiky@…, moonlimb@…||Triage Stage:||Accepted|
|Has patch:||yes||Needs documentation:||yes|
|Needs tests:||yes||Patch needs improvement:||no|
DateDetailView currently expects segments for year, month and day in the URL. This introduces the requirement to have an archive page for each level of the date; ie a year archive, a month archive, and a day archive:
I don't think I'm inaccurate in saying that most bloggers (as opposed to news sites) don't usually create more than one post a day, and many (myself included) have a frequency of much less than once per month. This means we're introducing views such as day archive that have exactly the same information as the higher levels. As a URL purist, I don't like unnecessary segments in my schema and unnecessary pages in my information architecture.
In my case my URL structure is as follows, I don't use DayArchive at all:
I've achieved this by creating my own version of DateDetailView that removes the use of DayMixin, but I think this can also be achieved by modifying DateDetailView itself to allow looser date matching using configuration of the view itself.
Is this a common enough use case to be worth making the change in Django itself? I think it can be done without affecting backwards compatibility.
Change History (7)
comment:4 Changed 4 years ago by
|Version:||1.3 → master|