You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reminder returns one armed alarm as a ScheduledReminder and reminders
lists every key of one operation, matching what the Ruby port already
offers. Both are async, because a TypeScript actor holds no rows and
reads its own through a reader the runtime supplies at hydration. That
is one injection point, so both engines get it: the SQL runtime reads
the reminders table for the instance, and the Durable Objects engine
reads the object's own store.
A read starts from the committed rows and applies the intents staged so
far, so an actor that schedules and then reads sees what the commit will
write, and one that cancels and then reads sees the alarm gone.
key and intervalMilliseconds are null rather than undefined. The first
draft used undefined and a test caught it: returning a ScheduledReminder
straight from an operation failed with InvalidPayload, because undefined
does not serialise. Returning one is the obvious thing to do, so the
type makes it work.
A projection has no reader and throws rather than reporting an armed
alarm as absent, which is the failure this whole feature exists to
prevent.
ScheduledReminder rather than ReminderStatus, because the
administration API already exports that name for the status string.
0 commit comments