In the TableSchema standard, constraints such as a fields being required or unique need to be specified within a constraints property (see documentation).
In all the dataresource.yaml files specify properties like required or unique directly under each field, which is allowed, but it means they don't have the intended meaning, i.e., frictionless will not consider them when validating the data.
What needs to be done is for any field that has required: true or unique: true, these need to be moved into a constraints property.
E.g. this
In the TableSchema standard, constraints such as a fields being required or unique need to be specified within a
constraintsproperty (see documentation).In all the
dataresource.yamlfiles specify properties likerequiredoruniquedirectly under each field, which is allowed, but it means they don't have the intended meaning, i.e.,frictionlesswill not consider them when validating the data.What needs to be done is for any field that has
required: trueorunique: true, these need to be moved into aconstraintsproperty. E.g. thisbecomes
Note that specifying
required: falseorunique: falseis not necessary as these are the case by default.