feat: Add User Email Column to Export Event Attendance as CSV feature

[DanielJEfres]

Context

Daniel is currently exporting the list of people who checked in for the Mentor Mixer, and attempting to diff them against the people who filled out the mentor preference form to see who attended and forgot to fill out the form in order to email all of them for a reminder.

i cant find user emails through attendee export ?

Problem

Unable to determine user emails through attendee export as CSV feature, attendance export only has member UUID, name, discord username, check in data, operator, and points.

Current pain points:

• Cannot find the correct user email to reach out to attendee list through

Desired UX

Support a new column which appends the user's email to the CSV:

Acceptance Criteria

• Admin can export attendee CSV & view email column per attendee

[coderabbitai]

Coding Plan

Summary

• Add email: Member.email to loadMinimalAttendees, which already joins Member.
• Add an "Email" header and cell to serializeAttendanceCsv, and pass email through in event.exportAttendance.
• Update the attendance CSV test that documents the current column set.
• Show email in the on-screen attendee list so the roster and the CSV stay consistent.

Note for follow-up agents: email is already reachable to holders of READ_CLUB_EVENT/EDIT_CLUB_EVENT via the roster, so this change adds no new permission boundary. The event.attendance.exported audit event now covers PII (email). Confirm this matches project PII/audit conventions.

Design Choices

Design Choice 1: Scope: CSV only or CSV and on-screen list?

Options Considered:

1. Add email to the CSV export only.
2. Add email to both the CSV export and the on-screen attendee list.

Chosen Option: 2

Rationale: The on-screen attendee list in event-detail-dialog.tsx uses the same query as the CSV. Both surfaces read from loadMinimalAttendees, so exposing email in both keeps the data consistent and satisfies the "view email column per attendee" wording. The on-screen change is small and requires no new query.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Phase 1: Add email to the attendance data and CSV export

Extend the shared attendance query to select member email. Thread the email value through the serializer and the export procedure. Update the test that pins the current column set.

Task 1: Select member email in the attendance query

Add the email field to the query that feeds both the CSV export and the on-screen roster.

• Update loadMinimalAttendees in packages/api/src/utils/events/queries.ts.
• Add email: Member.email to the .select({...}) projection.
• No new join is required. Member is already inner-joined.

Task 2: Add the Email column to the CSV serializer

Extend the CSV row shape and output to include email.

• Update serializeAttendanceCsv in packages/api/src/utils/events/attendance.ts.
• Add email: string to the row type.
• Add an "Email" header in the header row.
• Add row.email to each mapped data row in the same column position as the header.

Task 3: Pass email through the export procedure

Include email in the whitelisted field mapping before serialization.

• Update the event.exportAttendance mapping in packages/api/src/routers/event.ts.
• Add email: row.email to the object passed into serializeAttendanceCsv.

Task 4: Update the attendance CSV test

The existing test asserts the exact header string and asserts the CSV does not contain "Email". This test fails after the column is added.

• Update test [TC-023] in packages/api/src/tests/events/attendance.test.ts.
• Update the expected header row string to include the new Email column.
• Remove or invert the expect(csv).not.toContain("Email") assertion.
• Add an assertion that a sample email value appears in the output.

🤖 Prompt for AI agents

Add an Email column to the attendance data pipeline and the CSV export it feeds.

- In `packages/api/src/utils/events/queries.ts`, update `loadMinimalAttendees`.
Add `email: Member.email` to the `.select({...})` projection. Do not add a new
join; `Member` is already inner-joined.
- In `packages/api/src/utils/events/attendance.ts`, update
`serializeAttendanceCsv`. Add `email: string` to the row type. Add an "Email"
header to the header row. Add `row.email` to each mapped data row, at the same
column position as the header.
- In `packages/api/src/routers/event.ts`, update the `event.exportAttendance`
field mapping. Add `email: row.email` to the object passed into
`serializeAttendanceCsv`.
- In `packages/api/src/tests/events/attendance.test.ts`, update test `[TC-023]`.
Update the expected header row string to include the new `Email` column. Remove
or invert the `expect(csv).not.toContain("Email")` assertion. Add an assertion
that a sample email value appears in the output.

Phase 2: Show email in the on-screen attendee list

Display email next to name and Discord username in the attendee cards, so the roster matches the CSV.

Render email in the attendee card list

Add the email value to each attendee card.

• Update the attendee list rendering in apps/blade/src/app/_components/admin/events/event-detail-dialog.tsx.
• Display attendee.email alongside the existing name and @discordUsername fields.
• Confirm the client type for attendee rows includes the new email field. If a local type or the listAttendees mapping omits email, add it so the field is available.

🤖 Prompt for AI agents

Show the attendee email in the on-screen roster so it matches the CSV export.

- In `apps/blade/src/app/_components/admin/events/event-detail-dialog.tsx`,
update the attendee card rendering.
- Display `attendee.email` alongside the existing name and `@discordUsername`
fields.
- Check the client type for attendee rows. If a local type or the
`listAttendees` mapping omits the `email` field, add it so the field is
available for rendering.

Research

The Club event attendance export spans three layers. loadMinimalAttendees(eventId) in packages/api/src/utils/events/queries.ts fetches attendee rows and already inner-joins Member. serializeAttendanceCsv() in packages/api/src/utils/events/attendance.ts maps rows to CSV headers and cells through the shared serializeCsvRows encoder. The event.exportAttendance procedure in packages/api/src/routers/event.ts whitelists fields before serialization. The same query also feeds the on-screen attendee card list in apps/blade/src/app/_components/admin/events/event-detail-dialog.tsx. Member.email is a NOT NULL, unique column in packages/db/src/schemas/knight-hacks.ts. The export runs behind requireEventRead (READ_CLUB_EVENT/EDIT_CLUB_EVENT).

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

Add an Email column to the attendance data pipeline and the CSV export it feeds.

- In `packages/api/src/utils/events/queries.ts`, update `loadMinimalAttendees`.
Add `email: Member.email` to the `.select({...})` projection. Do not add a new
join; `Member` is already inner-joined.
- In `packages/api/src/utils/events/attendance.ts`, update
`serializeAttendanceCsv`. Add `email: string` to the row type. Add an "Email"
header to the header row. Add `row.email` to each mapped data row, at the same
column position as the header.
- In `packages/api/src/routers/event.ts`, update the `event.exportAttendance`
field mapping. Add `email: row.email` to the object passed into
`serializeAttendanceCsv`.
- In `packages/api/src/tests/events/attendance.test.ts`, update test `[TC-023]`.
Update the expected header row string to include the new `Email` column. Remove
or invert the `expect(csv).not.toContain("Email")` assertion. Add an assertion
that a sample email value appears in the output.
===============================================================================

Task: 2

Show the attendee email in the on-screen roster so it matches the CSV export.

- In `apps/blade/src/app/_components/admin/events/event-detail-dialog.tsx`,
update the attendee card rendering.
- Display `attendee.email` alongside the existing name and `@discordUsername`
fields.
- Check the client type for attendee rows. If a local type or the
`listAttendees` mapping omits the `email` field, add it so the field is
available for rendering.

💡 Iterate on the plan with: `@coderabbitai` <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---