#1302 closed enhancement (fixed)
[patch] archive_month should provide next_month and previous_month objects
| Reported by: | James Bennett | Owned by: | Jacob |
|---|---|---|---|
| Component: | Generic views | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The archive_day generic view provides 'next_day' and 'previous_day' date objects, which can be convenient when setting up navigation links in a date-based archive. It'd be even more convenient if the archive_month view provided 'next_month' and 'previous_month' date objects for the same purpose. The only problem I can see with this is that any datetime.date object will, by necessity, include a day component, which could be confusing, but so long as it's clear that these are to be used for their month and year components that shouldn't be a major issue.
Attachments (1)
Change History (3)
by , 19 years ago
| Attachment: | date_based.diff added |
|---|
comment:1 by , 19 years ago
| Summary: | archive_month should provide next_month and previous_month objects → [patch] archive_month should provide next_month and previous_month objects |
|---|
comment:2 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
patch to provide next_month and previous_month in archive_month generic view