Problem/Motivation

In #2794481: Allow end date to be optional we added a new setting optional_end_date in field storage config to allow end date to be optional in DateRangeItem. But because of this editors can't reuse this field in 2 places where 1 should have optional end date and the other not.

Steps to reproduce

Proposed resolution

Decide to shift the optional_end_date from field storage config. See https://www.drupal.org/project/drupal/issues/2794481#comment-12479617 and https://www.drupal.org/project/drupal/issues/2794481#comment-12482140 which discusses some specific problems with putting the setting on the field config and not the field storage config.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

kunal.sachdev created an issue. See original summary.

kunal.sachdev’s picture

kunal.sachdev commented
Title: Shift the optional_end_date setting to field config » Shift the optional_end_date setting from field storage config
kunal.sachdev’s picture

kunal.sachdev commented
Status: Active » Closed (won't fix)

Will be fixed in #2794481: Allow end date to be optional.

kunal.sachdev’s picture

kunal.sachdev commented
Status: Closed (won't fix) » Postponed

Decided to not do it in #2794481: Allow end date to be optional and hence it's now postponed on #2794481: Allow end date to be optional .

kunal.sachdev’s picture

kunal.sachdev commented
Status: Postponed » Closed (won't fix)

This is fixed in #2794481: Allow end date to be optional.