plugin-calendar: `ObjectCalendar` resolves `allDayField` into its `CalendarConfig` and never reads it — `allDay` is inferred from the absence of an end date, while the `calendar-view` sibling honours the key

[os-steve]

Filed unassigned, out of scope for objectui#7711 (filter.calendar retirement), found while auditing what getCalendarConfig can return. Measured on origin/main @ f5c8b8e, from the worktree of branch claude/issue-7711-calendar-config-key.

Measured

packages/plugin-calendar/src/ObjectCalendar.tsx resolves the key into the config it returns:

:168          allDayField: (schema as any).allDayField

and then never reads it back. The events pass destructures only four keys and infers the flag:

:527    const { startDateField, endDateField, titleField, colorField } = calendarConfig;
:603          allDay: !endDate, // If no end date, treat as all-day event

git grep -n "allDayField" packages/plugin-calendar/src/ObjectCalendar.tsx returns the resolution site and the memo dependency only — no consumer.

Why it matters

The key is declared, documented and plumbed, and it is silently dropped by this one renderer:

• Declared, and by the spec. CalendarConfig is re-exported straight from @objectstack/spec/ui (packages/types/src/objectql.ts:145, CalendarConfigSchema); packages/types/src/complex.ts:512 carries allDayField?: string with @default 'allDay' and the doc comment "Record field indicating an all-day event."
• Plumbed. packages/app-shell/src/views/ObjectView.tsx:2085 lists allDayField among the flat keys it flattens down onto the view, so an authored value does reach this component.
• Documented. packages/plugin-calendar/README.md:254 tells authors to "point titleField / startDateField / endDateField / allDayField / colorField at your own fields when they differ."
• Honoured by the sibling. packages/plugin-calendar/src/calendar-view-renderer.tsx:285,292 does exactly what the declaration says: const allDayField = schema.allDayField || 'allDay' then allDay: record[allDayField].

So two renderers in one package answer the same declared key two different ways. An author who sets allDayField: 'is_all_day' on an object-calendar gets the flag computed from whether the record happens to carry an end date instead — and a record with a real end date that IS flagged all-day renders as a timed event, with no diagnostic.

Not the same defect as objectui#5667 (which recorded calendar-view dropping declared CalendarViewSchema keys, and is closed): this is the opposite component and the opposite direction — calendar-view reads it, object-calendar does not.

⚠️ Not measured here: whether the inference at :603 is itself the ruled behaviour and the declaration is the thing that should go, or whether the read is simply missing. Both directions are open — that judgement is triage's, not this report's.

Refs: objectui#7711 (the card this was found under, which does not touch it).