context.session.$authorize() vs resolver.authorize()

[antonykamp]

Hey,
I thought, that context.session.$authorize() and resolver.authorize() are both verifying and validating the users' role and login-status. But when I try the following, the user is either a number or null (the login-status isn't validated) :/

import { Ctx, resolver } from "blitz"
export default resolver.pipe(resolver.authorize(), async ({ id }, context: Ctx) => {
  const user = context.session.userId  // user: number | null
})

When I use context.session.$authorize() instead user is a number (the login-status is validated).

import { Ctx, resolver } from "blitz"
export default resolver.pipe(async ({ id }, context: Ctx) => {
  context.session.$authorize()
  const user = context.session.userId  // user: number
})

I thought resolver.authorize() is based on context.session.$authorize()? But it doesn't validate the input like resolver.zod does. Am I doing something wrong?

antony :)

[flybayer]

Here's the fix. Don't use Ctx when you use resolver.x :)

-import { Ctx, resolver } from "blitz"
+import { resolver } from "blitz"
-export default resolver.pipe(resolver.authorize(), async ({ id }, context: Ctx) => {
+export default resolver.pipe(resolver.authorize(), async ({ id }, context) => {
  const user = context.session.userId  // user: number | null
})

[antonykamp]

Thank you so much 🙏

[oyatek]

why so and what's the type of context then? Should it be BlitzCtx?