## Summary
- Organizers can cancel events directly from the event list via PATCH API
- Confirmation dialog shows role-differentiated messaging ("Cancel event?" vs "Remove event?")
- 204, 409 (already cancelled), and 404 (event gone) all treated as successful removal
- 8 new E2E tests + 5 new unit tests, all green, no regressions
## Test plan
- [x] Unit tests: 151 passed (16 in EventList.spec.ts)
- [x] E2E tests: 79 passed (8 in cancel-event-list.spec.ts)
- [x] Exploratory browser testing against real backend (204, 404, 409 flows)
- [x] Existing attendee/watcher delete flows unchanged
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Organizers can now cancel events directly from the event list via the
existing PATCH /events/{eventToken} API. The confirmation dialog shows
role-differentiated messaging: "Cancel event?" with a severity warning
for organizers vs. "Remove event?" for attendees. Responses 204, 409,
and 404 all result in successful removal from the local list.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
nitrix
merged commit 5082ec1333 into master2026-03-13 16:27:51 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Test plan
🤖 Generated with Claude Code
Organizers can now cancel events directly from the event list via the existing PATCH /events/{eventToken} API. The confirmation dialog shows role-differentiated messaging: "Cancel event?" with a severity warning for organizers vs. "Remove event?" for attendees. Responses 204, 409, and 404 all result in successful removal from the local list. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>