Validation resolver cached?

[mortmoe]

I can see in the docs that the resolver should be cached on first render ("This function will be cached inside the custom hook, while context is a mutable object which can be changed on each re-render."). This means if I do this:

    const methods = useForm({
        mode: 'onBlur',
        defaultValues: initialValues,
        resolver: yupResolver(validationSchema)
    })

... and then "validationSchema" changes from undefined to a yup validator object will it change so validation start working?

The reason I'm asking is that I have a form that I use a jsonSchema to generate, and then I have some functions createYupSchemaFromJsonSchema(schema) and generateDefaultValueFromJsonSchema(schema). The schema is set depending on user interaction meaning that it's not there on the initial render. So... I ran into a problem with the defaultValues not being set and did some digging and found out that I had to use reset like this:

    useEffect(() => {
        methods.reset(initialValues)
    },[initialValues])

That fixed the defaultValue problem ... but what confuses me is that the validation works fine. Seems to me like changing the validationSchema (or actually setting it) changes the resolver. I mean... it works, but I don't understand why ... and I don't like things that work without understanding it, they tend to fail eventually :) Can anyone explain why this works?

[bluebill1049]

useForm({
  context: {xxx},
  resolver: async () => (data, context) => validate.xxx
})

i think this is you after?

[bluebill1049]

The context will be injected into resolver in the next release: (if that's what you refer to) react-hook-form/resolvers#30 and the current context is as intended, we are not going to change its behavior.

[mortmoe]

Kind of :) I was not implying that the current context is not as intended, but MY use in the function above might not be :) My issue isn't really with the context ... but that the schema might change after useForm is called.

[bluebill1049]

why not keep a set of schemes and use switch statements based on the context?

[mortmoe]

Hmm... problem is that the schema is dynamically generated based on data from back-end so it might not be available at the time we're calling useForm.

[mohanaprasadp]

@bluebill1049 I have a usecase where the validator needs to calculate a constraint dynamically based on another field value. for this, I have used a yup schema where I pass the required value to be added in the constraint like so

export const mySchema = maxReceivingWeight => {
	return yup.object().shape({
		weight: yup
			.number('Receiving Weight is not valid')
			.max(
				maxReceivingWeight,
				'Receiving Weight cannot be greater than' + maxReceivingWeight
			)
			.required('Receiving Weight is Required')
	});
};

Anyway I can do this?