View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002387 | Composr | core | public | 2016-04-09 14:59 | 2016-07-17 16:44 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002387: Refactor get_timezoned_date and get_timezoned_time | ||||
| Description | Currently the parameters are not in a logical order. Also we have DATE, DATE_TIME and TIME symbols, but only two functions. So maybe the functions should be get_timezoned_date, get_timezoned_date_time, get_timezoned_time. Also, is the concept of a verbose date actually useful? It might be better to only use the concisish format we currently use, then people can template in custom date formats as needed. This is more logical for get_timezoned_date_time... timestamp avoid_contextual_dates utc_time member The order of parameters for the symbols should match the function. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | 3 | ||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-04-09 14:59 | Chris Graham | New Issue | |
| 2016-04-09 16:28 | Chris Graham | Description Updated | View Revisions |
| 2016-04-09 17:27 | Chris Graham | Note Added: 0003542 | |
| 2016-07-17 16:44 | Chris Graham | Status | non-assigned => resolved |
| 2016-07-17 16:44 | Chris Graham | Resolution | open => fixed |
| 2016-07-17 16:44 | Chris Graham | Assigned To | => Chris Graham |
