Multi-schema nullable validators not working as expected.

[ccampanale]

I'm using [email protected] and attempting a multi-validator schema to represent the union type string | boolean | null while disallowing undefined but this is not working as I expect.

According to the docs:

If you want disallow undefined value but allow null value, use nullable instead of optional.

const schema = {
    dateString: [
        { type: "string", nullable: true },
        { type: "boolean", nullable: true }
    ]
}

check = v.compile(schema);

check({ dateString: true }); // Valid
check({ dateString: new Date().toISOString() }); // Valid
check({ dateString: null }); // Fail

The third test should pass since both schemas are nullable. Instead I see the follow results from the validator:

[
  {
    type: 'required',
    message: "The 'dateString' field is required.",
    field: 'dateString',
    actual: null
  }
]

Let me know if I a missing something and thanks for taking a look!

[icebob]

The nullable is not working with multi rule shorthand format, try this form:

const schema = {
	dateString: {
		type: "multi", rules: [
			{ type: "string" },
			{ type: "boolean" }
		], nullable: true
	}
};

[ccampanale]

@icebob Thanks for addressing this. The long form multi - which I honestly must have glossed over in the docs - works great.

[icebob]

Nop, by the way, the issue fixed in the latest version, so your original code can work as well.