Nested yup schema validation

[iamacook]

I'm currently migrating to react-hook-form and the current yup resolver does recognise yup's when in nested schemas.

I've created an example here. You should be able to submit the form because the condition has been met, but the resolver doesn't recognise it?

Love the work that you're doing! Thanks in advance for your help!

[bluebill1049]

we focus single input validation at all, for dependency validation, you need to use tirgger

[iamacook]

Thank you for getting back to me so quickly. I apologise for the late reply.

The initial validation was not the issue. Without passing the context to yup, it cannot retrieve the values of fields outside of the embedded schema.

I have since migrated from yup to joi, since you do not need to embed schemas inside schemas if you're data structure is made up of embedded objects.

[bluebill1049]

thanks, what's the remaining issue here?

[iamacook]

In the schema (taken from the example):

const schema = yup.object({
  firstName: yup.string().required(),
  test: yup.object({
    location: yup.string().when("firstName", {
      is: "Aaron",
      then: yup.string(),
      otherwise: yup.string().min(10)
    })
  })
});

The field 'test.location' in the schema cannot access the value of 'firstName' and returns undefined. So, it isn't possible to use when("xyz", { is: this condition... } in embedded yup schemas.

[bluebill1049]

I just succesfully submit the form.

[iamacook]

There should not be a character limit when the first field is 'Aaron'.

location: yup.string().when("firstName", {
    is: "Aaron",
    then: yup.string(),
    otherwise: yup.string().min(10)
})

[bluebill1049]

This is what yup returned.

[iamacook]

Maybe I'm confused, and I'm sorry if I am, but it shouldn't be returning that error because the field value is 'Aaron'? There is no character limit when that condition is met.

[bluebill1049]

there is no right or wrong here :) we just try to make it work, for RHF we just follow what's yup's returning.

[iamacook]

Ok, well the only way I could get it to work was by passing a continuously updated context to yup and that completely goes against the reason for my initial migration (reducing renders). I instead switched to Joi because you don't have to embed schema objects if your data structure has multi-level object(s).

Thank you for looking into this nonetheless. I'm really happy with the performance increase I've got after migrating from Formik!