From 732acb5b259ef875b4632e679b946e462df39db8 Mon Sep 17 00:00:00 2001 From: mohammed hussam <52914487+hussamkhatib@users.noreply.github.com> Date: Tue, 16 Aug 2022 04:05:44 +0530 Subject: [PATCH] fix: remove redundant AND (#3833) Co-authored-by: hussamkhatib --- apps/web/pages/[user]/[type].tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/web/pages/[user]/[type].tsx b/apps/web/pages/[user]/[type].tsx index e853d374f4..9641383760 100644 --- a/apps/web/pages/[user]/[type].tsx +++ b/apps/web/pages/[user]/[type].tsx @@ -99,7 +99,7 @@ async function getUserPageProps(context: GetStaticPropsContext) { slug, /* Free users can only display their first eventType */ id: user.plan === UserPlan.FREE ? eventTypeIds[0] : undefined, - AND: [{ OR: [{ userId: user.id }, { users: { some: { id: user.id } } }] }], + OR: [{ userId: user.id }, { users: { some: { id: user.id } } }], }, // Order is important to ensure that given a slug if there are duplicates, we choose the same event type consistently when showing in event-types list UI(in terms of ordering and disabled event types) // TODO: If we can ensure that there are no duplicates for a [slug, userId] combination in existing data, this requirement might be avoided.