Codex Comments - Answer Overflow

•Created by Codex on 8/22/2024 in #questions

React Error

Solved it, I guess typescript was just being stupid with that file (I had to delete it and recreate it for anyone who runs into this issue).

4 replies

TTCTheo's Typesafe Cult

•Created by Codex on 4/9/2024 in #questions

trpc context not passed correctly

Finally this is what is creating the session.

const createInnerTRPCContext = (opts: CreateContextOptions) => {
  return {
    session: opts.session,
    prisma,
  };
};

export const createTRPCContext = async (opts: CreateNextContextOptions) => {
  const { req, res } = opts;
  // Get the session from the server using the getServerSession wrapper function
  const session = await getServerAuthSession({ req, res });
  return createInnerTRPCContext({
    session,
  });
};

const createInnerTRPCContext = (opts: CreateContextOptions) => {
  return {
    session: opts.session,
    prisma,
  };
};

export const createTRPCContext = async (opts: CreateNextContextOptions) => {
  const { req, res } = opts;
  // Get the session from the server using the getServerSession wrapper function
  const session = await getServerAuthSession({ req, res });
  return createInnerTRPCContext({
    session,
  });
};

What is happening is that when the front end calls the session I properly get the role inside session.user.role. Moving from the front end to the actual API calls, the first time it creates the session in the middleware it is going through my session callback, and the session when logged DOES come with role and userId, However once it is returned it somehow loses those two values, and the context is set without those two. Any help is much appreciated thanks in advance. Setup: T3: Nextauth, Nextjs pages router, trpc, typescript and prisma. Node version: 18.18.1

3 replies

TtRPC

•Created by Codex on 4/9/2024 in #❓-help

Context is not being passed correctly

Finally this is what is creating the session.

const createInnerTRPCContext = (opts: CreateContextOptions) => {
  return {
    session: opts.session,
    prisma,
  };
};

export const createTRPCContext = async (opts: CreateNextContextOptions) => {
  const { req, res } = opts;
  // Get the session from the server using the getServerSession wrapper function
  const session = await getServerAuthSession({ req, res });
  return createInnerTRPCContext({
    session,
  });
};

const createInnerTRPCContext = (opts: CreateContextOptions) => {
  return {
    session: opts.session,
    prisma,
  };
};

export const createTRPCContext = async (opts: CreateNextContextOptions) => {
  const { req, res } = opts;
  // Get the session from the server using the getServerSession wrapper function
  const session = await getServerAuthSession({ req, res });
  return createInnerTRPCContext({
    session,
  });
};

What is happening is that when the front end calls the session I properly get the role inside session.user.role. Moving from the front end to the actual API calls, the first time it creates the session in the middleware it is going through my session callback, and the session when logged DOES come with role and userId, However once it is returned it somehow loses those two values, and the context is set without those two. Any help is much appreciated thanks in advance. Setup: T3: Nextauth, Nextjs pages router, trpc, typescript and prisma. Node version: 18.18.1

3 replies

TTCTheo's Typesafe Cult

•Created by Mocha on 3/5/2024 in #questions

TRPCClientError: Unexpected token 'A', "An error o"... is not valid JSON

It might be that vercel is timing out if you don't have the pro version

10 replies

TTCTheo's Typesafe Cult

•Created by Wiznet on 1/17/2024 in #questions

Next-auth.js: Redirect to custom URL after successful login.

You could probably force them out of it with a router.push("/home") not sure if its the best practice though

7 replies

TTCTheo's Typesafe Cult