Scheduling infrastructure for absolutely everyone.
fix: correct translation key for host and attendee emails (#19962)
amritdc3c7b43bf58
diff --git a/apps/web/modules/bookings/views/bookings-single-view.tsx b/apps/web/modules/bookings/views/bookings-single-view.tsxindex fd46527e553..8f0c95f0770 100644--- a/apps/web/modules/bookings/views/bookings-single-view.tsx+++ b/apps/web/modules/bookings/views/bookings-single-view.tsx@@ -322,12 +322,12 @@ export default function Success(props: PageProps) {const attendee = bookingInfo.attendees[0]?.name || bookingInfo.attendees[0]?.email || "Nameless";const host = bookingInfo.user.name || bookingInfo.user.email;if (isHost) {- return t(`${titlePrefix}emailed_host_and_attendees${titleSuffix}`, {+ return t(`${titlePrefix}emailed_host_and_attendee${titleSuffix}`, {user: attendee,});}if (isAttendee) {- return t(`${titlePrefix}emailed_host_and_attendees${titleSuffix}`, {+ return t(`${titlePrefix}emailed_host_and_attendee${titleSuffix}`, {user: host,});}@@ -336,7 +336,7 @@ export default function Success(props: PageProps) {attendee,});}- return t(`emailed_host_and_attendees${titleSuffix}`);+ return t(`emailed_host_and_attendee${titleSuffix}`);}// This is a weird case where the same route can be opened in booking flow as a success page or as a booking detail page from the app