There is no way to tell vee-validate our class instance is whole and no need for PartialDeepObject

[sharifzadesina]

What happened?

It seems there is no way to tell vee-validate to treat our class instance as a whole and not treat each property separately.
Imagine this:

<CountrySelect v-model="country" />

const schema = object({
  country: mixed((inp): inp is Country => inp instanceof Country).required().label('Country'),
});

const form = useForm({ validationSchema: toTypedSchema(schema) });

const [country] = form.defineField('country');

country ref is supposed to be of type Country | undefined, but it is of type PartialDeepObject<Country> | undefined.
the input, returns "country" as a whole or no country at all.

Reproduction steps

No response

Version

Vue.js 3.x and vee-validate 4.x

What browsers are you seeing the problem on?

• Firefox
• Chrome
• Safari
• Microsoft Edge

Relevant log output

No response

Demo link

No need

Code of Conduct

• I agree to follow this project's Code of Conduct

[sharifzadesina]

The one thing I can do is explicitly defining TValue, but this is not ideal, because vee-validate is supposed to get the type from yup:

const [country] = form.defineField<'country', Country>('country');

[logaretm]

This is a bit of a limitation sadly because there is no way for vee-validate to know if the country itself is the field or if it is a container for a bunch of fields.

Think about it like this, a phone object with name, flag properties can be expressed in two ways with fields:

• A select input that picks the country object from its options. The field emits the { name, flag } object as a value. This looks like your case here.
• Or a couple of nested fields country.name and country.flag and while this may not make sense in this example it does for other types of objects.

There is no way for vee-validate to know where the nesting stops and where the field is actually, all it knows that it has a schema and that schema leafs can be fields. So that's why it uses the PartialDeep type here.

Unless I work on a completely different schema validation system that takes this into account, I don't think I can do much here.

[sharifzadesina]

@logaretm Yup already treats the country as a whole when you use mixed validator. there is no problem in the schema validation part I suppose.
It is vee-validate that adds partial deep to everything.