Is there any way to access context provided by react-hook-form inside zod's superRefine?

[DiegoSaturno]

Context:

I have a validation on my form that depends on a calculated value, provided by an xstate selector. I tried to access it through zod's RefinementContext but wasn't able to do so.

Is there any way I can get this value inside superRefine? If not, is there any way I can write a custom resolver and merge it with zodResolver?

The code looks like this:

const mySchema = z.object({
   ...
}).superRefine((data, context) => {
  // I want to get `myCalculatedValue` here
});
type MySchema = z.infer<typeof mySchema>;

const calculatedValue = useSelector(actor, selector);

const methods = useForm<MySchema>({
  mode: "all",
  resolver: zodResolver(mySchema),
  context: {
    myCalculatedValue: calculatedValue,
  },
})

[vlanemcev]

Hi, @DiegoSaturno !

Any progress on this question? I'm trying to figure out how to do this correctly with Zod. Because in Yup library, for example, this approach is really common and easy to use.

[tunahanbayindir]

Any updates on this?

[Unknown47Dream]

Please add this.

[youbek]

Thanks for the library, but is there any updates/workarounds?

[jeremy-habit]

up ! pls

[kpauletti]

Any update on this? I really need this and i'd prefer not to use yup.

[landorid]

This is a must have in my opinion!

[JPG-2024]

totally

[landorid]

I would love to have this!

[brianMxBm]

Surprised this hasn't been added

[tfazekas]

Up! Please 🙏

[fstodulski]

Guys. I had the same issue.
Went with:

  const form = useForm<SubscriptionScheduleSchema>({
    resolver: zodResolver(subscriptionScheduleSchema(amountContext)),

where my schema is:

export const subscriptionScheduleSchema = (context: {
  minAmount: number;
  maxAmountOther: number;
  maxAmount: number;
}) =>
  newSubscriptionSchema
    .pick({

@tfazekas @brianMxBm @landorid

And it worked!

[tfazekas]

@fstodulski

Yeah... I know, but this case you cant infer type because the schema is dynamic:

export type SubscriptionScheduleSchemaType = Zod.infer<typeof subscriptionScheduleSchema>;

[fstodulski]

@tfazekas u can:
z.infer<ReturnType<typeof termsAndConditionsSchema>>>

[fstodulski]

It works like a charm

[tfazekas]

@fstodulski
Aaaah, you're right. Should have tried it out. I’m not really a fan of making the schema a function, as it often encourages teammates to create dynamic schemas.

It works for this case, but consider a scenario where a property is added conditionally based on a context—this would make it unclear to the TypeScript compiler whether that property is present or not.

So in this scenario, if react-hook-form would pass the context to zod and zod.schema's superRefine would receive that context, the schema can remain static.

[taksuparth]

@bluebill1049 any plan to add this?

[vansh-codes]

@bluebill1049 Exactly when can we expect thisss???

[idan1idan]

This is a must! please add a support for this.

[idan1idan]

Up!

[arnelyutiga]

Zod should support context just like Yup

[annanShao]

Have any progress?

[dimitriBouteille]

Apparently no solution since January 2024 ....

[BrendanC23]

colinhacks/zod#4745 (comment) is a response by the maintainer of Zod which states that "It's very unlikely any context mechanism gets added [to Zod]". The suggested workaround is:

function makeSchema(ctx: object) {
  return z.object({
      /// define 
  })
}

type Output = z.infer<ReturnType<typeof makeSchema>>;

As long as the schema isn't dynamic and has a consistent input/output types (it only uses the context within a refinement), this is a decent approach. Unless Zod changes to support external context, I don't think there's anything that react-hook-form can do to support this use-case.