From cfb92cbdd55238ffca921449a6ea065d68682a94 Mon Sep 17 00:00:00 2001
From: Hart <hartliddell@users.noreply.github.com>
Date: Wed, 27 Dec 2023 16:45:36 -0500
Subject: [PATCH] Update craftController.js

These debug statements were causing updateCraft to fail during my learning process.

Maybe it's here by design, but maybe it's not?
---
 graphql-backend/src/controllers/craftController.js | 2 --
 1 file changed, 2 deletions(-)

diff --git a/graphql-backend/src/controllers/craftController.js b/graphql-backend/src/controllers/craftController.js
index c94632c..ec0c366 100644
--- a/graphql-backend/src/controllers/craftController.js
+++ b/graphql-backend/src/controllers/craftController.js
@@ -50,8 +50,6 @@ exports.updateCraft = async (request, reply) => {
   try {
     const id = request.params ? request.params.id : request.id;
     const fields = request.body ? request.body : request;
-    await new Promise((resolve, reject) => setTimeout(reject, 2000));
-    // await new Promise((resolve) => setTimeout(resolve, 2000));
     const update = await Craft.findByIdAndUpdate(id, fields, { new: true });
     return update;
   } catch (error) {