You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different sites have different preferences for displaying dates and times. Further, different locales will treat dates and times differently.
The date-range and time-range display functions in eventtools (in utils.pprint_timespan) are pretty unwieldy, and difficult to replace with individual preference. This ticket is to implement an easier structure.
The proposal is to remove pprint_timespan, and define the range formats in a setting, which can be overridden or extended on a per-project basis:
Different sites have different preferences for displaying dates and times. Further, different locales will treat dates and times differently.
The date-range and time-range display functions in eventtools (in utils.pprint_timespan) are pretty unwieldy, and difficult to replace with individual preference. This ticket is to implement an easier structure.
The proposal is to remove pprint_timespan, and define the range formats in a setting, which can be overridden or extended on a per-project basis:
Then, in templates, the date can be formatted thus:
{{ events.pretty_date }} to use the DEFAULT format
{{ events.pretty_date_BRIEF }} to use the BRIEF format (using getattr magic).
The text was updated successfully, but these errors were encountered: