Repository navigation
feat(moderation): show event RSVPs in the moderation footprint - #267
Open
codeforphilly-bot wants to merge 2 commits into
Open
codeforphilly-bot wants to merge 2 commits into
codeforphilly-bot wants to merge 2 commits into
Conversation
The roster row carries an RSVP count and the member detail lists each RSVP with its event. Response shape only: no sheet contract changes. Specs, tests and a plan that ends done are included. Closes #266 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This branch has not been 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
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.
Shows event RSVPs in the moderation footprint, so staff reviewing an otherwise empty account can see that the person signed up for an event. Closes #266.
What changes
GET /api/admin/membersrows gainfootprint.rsvps, a count.GET /api/admin/members/:sluggainsfootprint.rsvps, a list of{ event: { slug, title, startsAt }, createdAt }, newest RSVP first. Past and cancelled events are included. Agent callers see the same list; it holds only public event fields.1 RSVPor3 RSVPswhen there are any. The detail panel gets an "Event RSVPs" section linking each event.specs/api/moderation.mdandspecs/screens/admin-members.mdfor the above.person-lifecycle.mdandspam-exclusion.mdnow say that a purge and the offline prune delete RSVPs, which the code already did.plans/moderation-footprint-rsvps.md, done.Response shape only. No sheet contract changes, and no new index: the existing
rsvpsByPersonserves it.Not in this change
has-footprint, and no scoring, review filter, agent rule or purge behaviour changes. Whether an RSVP should be a "not spam" signal is a follow-up in the plan.Verification
npm run type-check && npm run lint && npm run -w packages/shared check-contracts && npm testexits 0: 18 contracts match, 735 API tests, 191 web, 120 shared.plans/README.mdprefers the spec change first; say if you want it split.🧡🤖 Opened by GrittyBot, Code for Philly's ops bot. I am an AI. A person merges this.
🤖 Generated with Claude Code