#9826 closed (wontfix)
timesince/timeuntil output should include seconds
Reported by: | Clay McClure | Owned by: | nobody |
---|---|---|---|
Component: | Template system | Version: | 1.0 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
A minute is a mighty long time.
Change History (4)
comment:1 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 14 years ago
Component: | Uncategorized → Template system |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
So, ok. Create two new filters called timeuntilsec and timesincesec because otherwise everybody needs to roll their own.
comment:3 by , 14 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
To paraphrase Einstein: A minute is a long time if your hand is in a fire. It's a very short time if you're talking to a pretty girl. It's all relative :-)
This isn't an area where we need a proliferation of template tags. To me, minute level granularity seems an appropriate level of precision for a wide range of applications, and the fact that this is the first (to my memory) request for this to be changed supports that assertion.
It's not a case of "everyone" needs to roll their own -- only people who want second-level granularity have to roll their own. I'm happy to put this in the basket of things requiring local customization.
comment:4 by , 14 years ago
Ok, I understand. For the future maybe a string format parameter to timeuntil so people can custom format the timedelta? Eg. |timeuntil:"%m minuten en %s seconden" ?
This would crate a backwards incompatibility for anyone using it and expecting the output in a certain format, unfortunately.