Reason for change

Yup typically uses the schema.validate(values, { context }) pattern, which naturally leads users to try yupResolver(schema, { context }). However, yupResolver in @hookform/resolvers does not recommend using schemaOptions.context and overrides it with the form context provided by useForm({ context }) (there is a dev warning in the code), and this is not clearly documented in the README. This can increase debugging cost for users.

What’s changed

• Added a short explanation in the Yup section of the README on how to pass context.
• Clarified that context should be provided via useForm({ context }), and that this value is injected into Yup’s validation context at resolver execution time, with an example.
• Briefly clarified that schemaOptions.context is overridden by the form context, so context should be passed via useForm({ context }) instead.

Scope of impact

• Documentation-only change (no behavior changes).

References

• Dev warning inside yup resolver:

  resolvers/yup/src/yup.ts

  Line 100 in 2e9bc7c

  "You should not used the yup options context. Please, use the 'useForm' context object instead",

• fixes: Document yupResolver context handling in react-hook-form/resolvers #834