From c109ab1e3064cd917f85132b42416ad4de74580a Mon Sep 17 00:00:00 2001
From: Rory Hughes <544628+rorhug@users.noreply.github.com>
Date: Mon, 6 Dec 2021 13:25:22 +0000
Subject: [PATCH] Ensure credential objects come oldest first (#1258)

Given the credentials are loaded based on userId, sort is not consistent.
Without this, events are booked on whichever calendar credential is loaded first.
https://github.com/calendso/calendso/blob/813eaa83b7b4813c1854d20680f96d56e1016af0/lib/events/EventManager.ts#L240-L244

Co-authored-by: Bailey Pumfleet <pumfleet@hey.com>
---
 pages/api/book/confirm.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/pages/api/book/confirm.ts b/pages/api/book/confirm.ts
index 930af129..7aa599bb 100644
--- a/pages/api/book/confirm.ts
+++ b/pages/api/book/confirm.ts
@@ -63,7 +63,9 @@ export default async function handler(req: NextApiRequest, res: NextApiResponse)
     },
     select: {
       id: true,
-      credentials: true,
+      credentials: {
+        orderBy: { id: "desc" as Prisma.SortOrder },
+      },
       timeZone: true,
       email: true,
       name: true,