feat: automate event lifecycle transitions on start/end time - #79
Merged
Conversation
- Add events.end_date (nullable timestamptz) via migration. - Add ActivateDueEvents / ArchiveEndedEvents queries: draft -> scheduled when event_date has passed, scheduled -> archived (+ archived_at) when end_date has passed. - Add a polling worker (app/worker/event_lifecycle) that runs both transitions every EVENT_LIFECYCLE_POLL_INTERVAL_SECONDS (default 60s), wired into make run-workers. - Thread end_date through EventCreate/EventResponse/UserEventResponse and CreateEvent/GetUserEvents. Events with no end_date set are never auto-archived and stay in scheduled until archived manually via the existing endpoint.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
events.end_date(nullabletimestamptz) via migration.ActivateDueEvents/ArchiveEndedEventsqueries:draft→scheduledonceevent_datehas passed,scheduled→archived(+archived_at) onceend_datehas passed.app/worker/event_lifecycle) that runs both transitions everyEVENT_LIFECYCLE_POLL_INTERVAL_SECONDS(default 60s), wired intomake run-workers.end_datethroughEventCreate/EventResponse/UserEventResponseandCreateEvent/GetUserEvents.Events with no
end_dateset are never auto-archived and stay inscheduleduntil archived manually via the existing endpoint — worth telling admin/frontend that setting an end date is what enables auto-archiving.Test plan
make m-up),end_datecolumn confirmed in schemadraft → scheduledandscheduled → archived(witharchived_atset) both fired correctlymake run-workers, runs its first pass on schedule