You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but still wouldn't cover bizarre capitalization permutations (TRUe) like the previous behavior.
Would you (Joi team) be open to a PR that makes truthy and falsy values entered be case insensitive? I'm willing to do it but want to make sure it fits into the project's roadmap.
joi version: 10.0.0
used with (hapi, standalone, ...): hapi
The text was updated successfully, but these errors were encountered:
It wouldn't be a problem but we don't want to break our old APIs that use the old Joi validators. Probably no one would notice 'yes' and 'no' going away but using the strings 'true' and 'false' probably would. We joked that there should be a Joi.booleany() that has the <10.0 boolean behavior.
Context
In the
10.0.0
release notes it is said that the pre 10.0.0 functionality can be achieved with:This is not quite the same as the old schema as the new implementation with
set
doesn't use the insensitive flag when checking for set membershipjoi/lib/boolean.js
Line 31 in aff2519
but still wouldn't cover bizarre capitalization permutations (
TRUe
) like the previous behavior.Would you (Joi team) be open to a PR that makes
truthy
andfalsy
values entered be case insensitive? I'm willing to do it but want to make sure it fits into the project's roadmap.The text was updated successfully, but these errors were encountered: