Files
calendar/packages/prisma/selects/payment.ts
T
2fcb8a750d fix: cascade organization hideBranding setting to user and team events (#21703)
- Add utility function for cascading hideBranding logic
- Update all getServerSideProps files to check organization hideBranding as fallback
- Ensure team queries include parent hideBranding data
- Fix hideBranding not working for organization members and teams

Fixes the issue where organization-level branding settings were not
being applied to user and team event pages when the direct entity
didn't have hideBranding enabled.

Co-authored-by: Hariom Balhara <hariombalhara@gmail.com>
2025-06-12 09:14:55 -03:00

79 lines
1.6 KiB
TypeScript

import { Prisma } from "@prisma/client";
export const paymentDataSelect = Prisma.validator<Prisma.PaymentSelect>()({
data: true,
success: true,
uid: true,
refunded: true,
bookingId: true,
appId: true,
amount: true,
currency: true,
paymentOption: true,
booking: {
select: {
id: true,
uid: true,
description: true,
title: true,
startTime: true,
endTime: true,
responses: true,
user: {
select: {
name: true,
timeZone: true,
},
},
attendees: {
select: {
email: true,
name: true,
timeZone: true,
},
},
eventTypeId: true,
location: true,
status: true,
rejectionReason: true,
cancellationReason: true,
eventType: {
select: {
id: true,
title: true,
description: true,
length: true,
eventName: true,
requiresConfirmation: true,
userId: true,
metadata: true,
users: {
select: {
id: true,
name: true,
username: true,
hideBranding: true,
theme: true,
},
},
team: {
select: {
name: true,
hideBranding: true,
parent: {
select: {
hideBranding: true,
},
},
},
},
price: true,
currency: true,
successRedirectUrl: true,
forwardParamsSuccessRedirect: true,
},
},
},
},
});