Support code datetime & timestamp field types

Created on 6 May 2024, 8 months ago

Updated 6 September 2024, 4 months ago

Problem/Motivation

Now that we can turn things like "7:00pm" into "7pm" (see ✨ Option to conditionally drop minutes (when :00) and am/pm from time Fixed ), there is a use case for this formatter to work with individual datetime/timestamp fields as well as ranges.

Proposed resolution

Add datetime and timestamp to the list of field types supported by the daterange_compact field formatter.

Remaining tasks

Code + test coverage.

User interface changes

None.

API changes

None. The formatter service already copes with identical start and end values. It considers these as one date or timestamp and doesn't try to render it as a range.

Data model changes

None.

📌 Task

Status

Fixed

Version

2.1

Component

Code

Created by

🇸🇪Sweden erik.erskine

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @erik.erskine
Comment 8 months ago →
🇸🇪Sweden erik.erskine
erik.erskine → changed the visibility of the branch support-non-range-fields-3445445 to hidden.
Comment 8 months ago →
🇸🇪Sweden erik.erskine
erik.erskine → changed the visibility of the branch support-non-range-fields-3445445 to active.
Comment 4 months ago →
System Message

ffc0d712 committed on 2.1.x
Support core datetime & timestamp fields (#3445445)
Status changed to Fixed 4 months ago5:57pm 23 August 2024
Comment 4 months ago →
🇸🇪Sweden erik.erskine
Comment 4 months ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024