Joi vs Yup comparison of core schemas

[HamzaM3]

I have done a comparison of Joi and Yup core schemas. I have noticed a few things :

• Yup.string accepts all types and people don't expect that at start. It would be cool if it would be stricter in the type testing and also allow for parsing the string (strict option is too strict)
• Yup.number validates arrays with their first elements being a number. I think it's because of toString in the checking.
• Yup.bool accepts 0 and 1, I find this to be unexpected and it's not mentioned in the documentation
• There is no alternative type.

I think it would be cool if it was possible to add a way to be strict on the type testing while allowing parsing (maybe there is already).

Here's the comparison : https://github.com/HamzaM3/joi-yup-comparison

Thank you all for your work

[HamzaM3]

I have also found a bug with nonNullable as it is unavailable.

Yup version : ^0.32.11
Executed with node v16.0.0
My code:

const Yup = require('yup')
Yup.number().nonNullable() // throws nonNullable is not a function (it's value is undefined)
Yup.number().nullable().nonNullable() // throws nonNullable is not a function (it's value is undefined)

[jquense]

does this bug exist in the v1?

[HamzaM3]

No not anymore, but the array to number bug is still there:

Yup.number().validate([3, 'str']) // validates 3

[jquense]

Do you want to try and put up a PR to address that bug?

[HamzaM3]

Yes

[HamzaM3]

I finally had the time to take care of this, check out the pull request.