mixed.oneOf doesn't respect nullable

The mixed.oneOf doesn’t accept null when nullable is added.

Example

const fruitsOrNone = yup.string().oneOf(['apple', 'banana']).nullable(true)

fruitsOrNone.validate(null) // => throws ValidationError: 'this must be one the following values: apple, banana'
fruitsOrNone.validate('apple') // => apple

Expected

It’s expected to accept the value null when nullable is set on the schema.

[jquense]

yes this confusing but expected. you have a contradiction between your schema on one hand you are saying its can only be ‘apple’ or ‘banana’ and on the other say it can also be null, the best way to handle this is to add null to your oneOf config

[catamphetamine]

Ha ha, imagine how many dev hours you’ve wasted just by being stubborn and not handling this case automatically inside the library code.

... DEV DAYS WASTED BECAUSE OF ONE OF
NOT BEING ABLE TO HANDLE NULLS PROPERLY

Next person in this issue can increment the counter.