Improve type safety in event attendees mapping

[Harxhit]

Summary

Add proper typing for the attendee parameter in the attendees mapping logic to remove the implicit any TypeScript warning and improve type safety.

Contexts

The /api/events/:slug/attendees route currently maps over event.attendees, but the attendee parameter inside .map() is inferred as any, causing the TypeScript warning:

Parameter 'attendee' implicitly has an 'any' type.

This issue focuses on adding proper typing for the attendee object returned from Prisma so the mapping logic is fully typed and safer to maintain.

Tasks

• Identify the attendee type returned from Prisma query
• Add explicit typing for the attendee parameter or infer it correctly from Prisma
• Ensure TypeScript and lint checks pass without implicit any warnings

Acceptance Criteria

• attendee no longer has implicit any type
• Mapping logic remains unchanged in behavior
• TypeScript passes without related warnings
• Tests added or updated if needed
• Docs updated (if needed)

Area

backend

Difficulty

good first issue

[pari7maheshwari]

hey @Harxhit i would like to work on this issue under gssoc'26.Can uplease assign it to me .

[pari7maheshwari]

hey @Harxhit I looked into the issue. The warning is occurring because TypeScript is not able to infer the type of the attendee parameter inside the event.attendees.map() callback, so it falls back to any.

My approach is to properly type the Prisma query result instead of manually typing the callback parameter. Since the query already includes the attendees relation, Prisma can provide the exact return type for the event object along with its attendees.

By using Prisma’s generated payload type for the query result, TypeScript will automatically infer the correct type for each attendee in the mapping logic. This removes the implicit any warning while keeping the existing behavior and mapping logic unchanged.

This approach also improves long-term maintainability because the types remain automatically synced with future Prisma schema changes, avoiding the need for manual interfaces or unsafe any usage.

[Harxhit]

@pari7maheshwari I have assigned this issue to you.