Django

Code

Ticket #1302 (closed: fixed)

Opened 3 years ago

Last modified 2 years ago

[patch] archive_month should provide next_month and previous_month objects

Reported by: ubernostrum Assigned to: jacob
Milestone: Component: Generic views
Version: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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

date_based.diff (0.9 kB) - added by ubernostrum on 01/31/06 20:33:06.
patch to provide next_month and previous_month in archive_month generic view

Change History

01/31/06 20:33:06 changed by ubernostrum

  • attachment date_based.diff added.

patch to provide next_month and previous_month in archive_month generic view

01/31/06 20:33:41 changed by ubernostrum

  • summary changed from archive_month should provide next_month and previous_month objects to [patch] archive_month should provide next_month and previous_month objects.

02/17/06 12:03:55 changed by adrian

  • status changed from new to closed.
  • resolution set to fixed.

(In [2323]) Fixed #1302 -- Added next_month and previous_month to template context in archive_month date-based generic view. Thanks, ubernostrum

Add/Change #1302 ([patch] archive_month should provide next_month and previous_month objects)




Change Properties
Action