feat: extend recurring event window to 30 days, cascade delete recurrences - #46
Merged
Merged
Conversation
…te to upcoming occurrences Recurring events previously only materialized 1 day ahead, so volunteers couldn't see upcoming shifts more than a day out. Extends the cron job's window to 30 days (shared constant in recurring-events-config.ts) so daily/weekly/biweekly/monthly patterns populate further in advance. Deleting one occurrence of a recurring series now also soft-deletes the rest of that series' occurrences within the same 30-day window, so admins don't have to delete each future occurrence individually. The delete confirmation dialog now warns when a delete will cascade. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
src/lib/recurring-events-config.ts) shared by both the materialization cron job and the delete cascade, so they always stay in sync.Why
Client feedback: recurring events were only visible 24 hours before they occurred, and deleting a single occurrence of a recurring series required deleting each future occurrence one at a time.
Test plan
tsc --noEmitpassesnext lintpasses with no warnings/errorsNo database schema changes - no migration required.
🤖 Generated with Claude Code