Problem/Motivation

Currently, the end date of an event is always equal to the start date.

Proposed resolution

Find out if core makes it possible to define an end date somewhere. If yes, use it. If not, decide what to do.

Remaining tasks

- do the research

Comments

Anonymous’s picture

Anonymous (not verified) commented

pjonckiere created an issue. See original summary.

Anonymous’s picture

Anonymous (not verified) commented

There is a discussion on this here: #2161337: Add a Date Range field type with support for end date

Afaik, there currently is no implementation though.

Anonymous’s picture

Anonymous (not verified) commented

Formulated a more general question here: #2613454: Port Date module functionality missing from 8.x core

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Status: Active » Postponed

Postponing for now to see what happens either in core or Date 8.x

There is new class \Drupal\calendar\DateFieldWrapper. For now the getEndTimeStamp in this class just calls getStartTimeStamp. So in the future we could update getEndTimeStamp to get the real end timestamp. Outside of this class logic can assume that the start and end might be different.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented

Work has now started in core via #2161337: Add a Date Range field type with support for end date. That's what we're waiting for.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented
Status: Postponed » Closed (duplicate)

I'm assuming we don't need to keep this ticket open given #2699477: Steps towards handling end dates in Calendar 8.