Closed amelie-rondot closed 3 weeks ago
For more context, frictionless validate
is used in Validata.fr project. We want to upgrade frictionless-py
to v5 in this project. But if we do that now, the field-error
exposed in this issue will block many schemas used in this project.
Overview
Using frictionless validate I got this unvalid report of validation:
The error is related to the value given in the
example
property of the field 'IsTrue' of typeboolean
in the schema used for the validation, which is not valid.I was expected a valid report of validation: I was not expected an field-error on this value
example
which matches with thefalseValues
property value, as mentionned in theboolean
type of TableSchema documentation.Resources used to reproduce the problem
schema.json:
Note
Replacing in the schema field 'IsTrue' the optionnal property
example
with 'false' instead of 'no' solves the problem. The validation report is now valid with this new schema:As specified in the TableSchema boolean type documentation : "The boolean field can be customised with these additional properties:
trueValues: [ "true", "True", "TRUE", "1" ] falseValues: [ "false", "False", "FALSE", "0" ]
format
: no options (other than the default)."But, in this case the
falseValues
property seems to not be applied on theexample
property by frictionless and retruns an unexpected field-error in the validation report.