My use case: I collect date and time values for events. Sometimes, these events are posted when the date is known, but the time is (at that moment) unknown.

What I want to do is a single field that would collect the date and time, but allow for some of those fields to be blank. I can make the field optional already, but if the fields are partially filled in (i.e. if there's just a date) then it will error unless they're all filled in.

The workaround is of course to create two fields, one for date, and one for time, but that irks me from a data structure perspective. It'd be great to have non-required date fields, at least, allow for some empty fields.

Comments

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
CreditAttribution: rootwork commented

I should note that this is somewhat related to #259308: Allow "fuzzy" granularity, in that if a fix were committed for that, it would address this as well. But this is a more specific use case, and I think sidesteps the issue (in that issue) of ending up with nonstandard date values like a month-year pair without a day.

In the case of my suggestion, we'd just end up with day-month-year but no time, which would still be a valid date value.