Can i use redirects in mutations?

[niklasgrewe]

Hi everyone,
i use a mutation for login. New users who have not yet set a username etc. should be redirected to another page. Can I do redirects only with res.redirect or in the getServerSideProps function but not in mutations? I would like to set redirects directly in the mutation function, like this:

export default resolver.pipe(resolver.zod(Login), async ({ email }, ctx) => {
  const user = await authenticateUser(email)
  await ctx.session.$create({ userId: user.id, role: user.role as Role })
  
  if (!user.username) {
     return {
        redirect: {
           destination: "anotherpage"
           permament: false
        }
     }
  }
  return user
})

[flybayer]

Currently that's not possible, and it's unlikely we will change it. Queries and mutations are set up to not expose http by default.

In your case here, I suggest doing the redirect on the client right after login. Or possibly even adding the username to the session publicData and then have a declarative hook that redirects to a setup page if username is missing.

[niklasgrewe]

thank you, good to know 😊👍 but if I ever need useQuery, how can I do that with the caching then? I read online that some use memory-cache etc.. Is something like this recommended? are there better methods?

[flybayer]

@niklasgrewe what caching are you talking about here? We have support to prefetchQuery inside gSSP which lets you use useQuery but without the initial loading flash: https://blitzjs.com/docs/query-usage#prefetching

[niklasgrewe]

@flybayer what do you mean with gSSP - getServerSideProps? What about when making db queries like this?

export const getServerSideProps = async ({ req, res }) => {
  const session = await getSession(req, res)
  const result = await db.user.findUnique({
    where: { id: session.userId! },
    select: { email: true },
  })
  if (!session.username) {
    return {
      redirect: {
        destination: `/welcome?email=${result?.email}`,
        permanent: false,
      },
    }
  }
  return { props: {} }
}

can blitz also prefetch/cache this kind of queries? Is this approach recommend?

[MrLeebo]

If you are looking to cache database queries and other server operations like remote API calls, you're probably better off spinning up an instance of redis and caching your results there.

However, you probably wouldn't do that for something like this findUnique call, where the query is just seeking on an indexed column; the cost of accessing and writing the cache is probably more expensive than the DB call would be.

You'd want the cache for more complex reports (the kind of queries you would write in SQL directly instead of using the ORM)

Implementation-wise, using redis with blitz is not any different from how you'd use it in any other framework.

[flybayer]

@niklasgrewe that code snippet you have is a great way to handle it