Add RSVP feature: submit RSVP, block on expired events #16
Reference in New Issue
Block a user
Delete Branch "008-rsvp"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
EventToken,OrganizerToken,RsvpToken) with full codebase refactoringPOST /events/{token}/rsvps) with attendee countexpiryDate > eventDatevalidation withExpiryDateBeforeEventExceptionClockinRsvpServiceandEventServicefor deterministic testsTest plan
mvnw verifygreen (SpotBugs 0, Checkstyle 0)npm run buildgreen (type-check + Vite)🤖 Generated with Claude Code
Introduce typed token value objects (EventToken, OrganizerToken, RsvpToken) and refactor all existing Event code to use them. Add POST /events/{token}/rsvps endpoint that persists an RSVP and returns an rsvpToken. Populate attendeeCount in GET /events/{token} from a real count query instead of hardcoded 0. Includes: OpenAPI spec, Liquibase migration (rsvps table with ON DELETE CASCADE), domain model, hexagonal ports/adapters, service layer, and full test coverage (unit + integration). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>