Reminder with reminderMinutesBeforeStart = 0 is ignored due to falsy check

Description

When creating a calendar event with reminderMinutesBeforeStart explicitly set to 0, the reminder is silently ignored. This happens because the reminderTime calculation relies on a truthy check, causing valid numeric values like 0 to be treated as if no reminder was configured.

Current Behavior

If an event is created with:

reminderMinutesBeforeStart: 0

The following logic is executed:

const reminderTime = minutes ? getShiftedTime(startTime, -minutes) : undefined;

Since 0 is a falsy value in JavaScript/TypeScript, reminderTime becomes undefined.

As a result:

• reminderMinutesBeforeStart is stored as 0
• reminderTime is not generated
• No notification is scheduled

Expected Behavior

A value of 0 should be treated as a valid input, representing an immediate reminder at the event start time.

For example:

startTime = 10:00
reminderMinutesBeforeStart = 0

Expected:

reminderTime = 10:00

Root Cause

The condition:

minutes ? getShiftedTime(...) : undefined

incorrectly filters out valid values like 0. The logic checks for truthiness instead of checking whether a numeric value was provided.

Proposed Fix

Replace the falsy check with an explicit undefined/type check:

const reminderTime =
minutes !== undefined ? getShiftedTime(startTime, -minutes) : undefined;

This ensures that 0 is handled correctly while preserving existing behavior.

Locate the reminderTime calculation that uses minutes in the calendar event creation flow and trace how its result reaches notification scheduling. Verify that an explicit value of 0 produces a reminderTime equal to startTime, while an omitted value still produces no reminder; add or run the relevant reminder tests if available.