❓-help

Context being destroyed in mutator

HHax

9/21/2023

Im currently building an app using the t3 stack + clerk for auth I have an operation which relies on a user's id being passed in my trpc backend, which on other routers was being passed fine through the context object Specifically within this router and this mutator method, I am getting the values from context up until my prisma method is called (I think) and then they disappear. The mutator method is getting the context value, as I console.logged it before hitting this specfic api route Things attempted: - Merge existing ctx object with new ctx object - run middleware as async with awaits, - Any sort of insight or other things I can try is appreciated Code snippets in comments

Solution:

Solution: pass uid in from frontend using custom hook

Jump to solution

HHax

9/21/2023

Code snippets: Error Msg (Undefined property):

tRPC failed on workoutLog.createLog: [
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "sets",
      0,
      "userId"
    ],
    "message": "Required"
  },

tRPC failed on workoutLog.createLog: [
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "sets",
      0,
      "userId"
    ],
    "message": "Required"
  },

Mutator Method:

   createLog: protectedProcedure
    .input(workoutSchema)
    .mutation(async({ctx, input}) => {
        const {notes, workoutName, trainingPlanId, sets} = input;
        const {userId} = ctx.auth
        const userIdSets = sets.map(set => {return {...set, userId}})
        try {
            // context exists until here... where it's getting destroyed
            const dbLog = await prisma.workoutLog.create({
                data: {
                    trainingPlanId,
                    notes,
                    name: workoutName,
                    authorId: userId,
                    sets: {
                        createMany: {
                            data: userIdSets
                        }
                    }
                }
            })
            return dbLog;
        } catch (err) {
            return {err: err, ctx: ctx}
        }
    }),

   createLog: protectedProcedure
    .input(workoutSchema)
    .mutation(async({ctx, input}) => {
        const {notes, workoutName, trainingPlanId, sets} = input;
        const {userId} = ctx.auth
        const userIdSets = sets.map(set => {return {...set, userId}})
        try {
            // context exists until here... where it's getting destroyed
            const dbLog = await prisma.workoutLog.create({
                data: {
                    trainingPlanId,
                    notes,
                    name: workoutName,
                    authorId: userId,
                    sets: {
                        createMany: {
                            data: userIdSets
                        }
                    }
                }
            })
            return dbLog;
        } catch (err) {
            return {err: err, ctx: ctx}
        }
    }),

Middleware/Context (trpc.ts)

const enforceUserIsAuthed = t.middleware(async({ ctx, next }) => {
  if (!ctx.auth.userId) {
    throw new TRPCError({ code: "UNAUTHORIZED" });
  }
  return await next({
    ctx: {
      auth: ctx.auth
    },
  });
});

const enforceUserIsAuthed = t.middleware(async({ ctx, next }) => {
  if (!ctx.auth.userId) {
    throw new TRPCError({ code: "UNAUTHORIZED" });
  }
  return await next({
    ctx: {
      auth: ctx.auth
    },
  });
});

interface AuthContext {
  auth: SignedInAuthObject | SignedOutAuthObject
}

const createInnerTRPCContext = ({auth} : AuthContext) => {
  return {
    prisma,
    auth,
  }
}

/**
 * This is the actual context you will use in your router. It will be used to process every request
 * that goes through your tRPC endpoint.
 *
 * @see https://trpc.io/docs/context
 */
export const createTRPCContext = (opts: CreateNextContextOptions) => {
  const { req, res } = opts;
  return createInnerTRPCContext({auth: getAuth(req)});
};

interface AuthContext {
  auth: SignedInAuthObject | SignedOutAuthObject
}

const createInnerTRPCContext = ({auth} : AuthContext) => {
  return {
    prisma,
    auth,
  }
}

/**
 * This is the actual context you will use in your router. It will be used to process every request
 * that goes through your tRPC endpoint.
 *
 * @see https://trpc.io/docs/context
 */
export const createTRPCContext = (opts: CreateNextContextOptions) => {
  const { req, res } = opts;
  return createInnerTRPCContext({auth: getAuth(req)});
};

Solution

HHax

9/21/2023

Solution: pass uid in from frontend using custom hook

Looking for more? Join the community!

❓-help

❓-help

Recommended Posts

Optimizing Data Refresh with trpc in React/Nextjs? Is there a more efficient way?I'm working on a Nextjs project using trpc, and I've noticed that I'm repeating the same code for da corsHi! Some problems with cors maybe you can help, ```readingbee.se/:1 Access to fetch at 'https://serv Showing pending inside the request?I am using trpc with nextjs but when I am using hooks they're just not returning anything? Like it m Output properties missing on frontend results (Type Infer)My trpc client is inferring the type without some properties from the object (See images for explen Avoid checking for TRPCClientError, and return the error in client query/mutateWhat i'm trying to do, is avoid doing try/catch on every trpc call to backend, if ZOD validation fai Property 'query' does not exist on type ...I think this is an issue on my end here is how I am defining everything ``` export const t = initTRP useQueries passing ctx data to splitLink not workingWhen tRPC is implemented with splitLink using useQueries does not pass cxt parameters to splitLink. Build and Publish on lambda from Github ActionsTrying to send my TRPC API on Lambda AWS + API Gateway. I have follow the documentation. But now ho next-pwa with trpc and push notificationHow can I build an app with next-pwa, trpc and push notification?Forced router input?I have a user route which has routes like get, delete, create etc. Some of the routes I require extr