Type validation of fields with an undefined value fails

[jfbenckhuijsen]

Type validation of fields with an undefined value fails

[sebelga]

Did you put required:true in the Schema for that property?

[sebelga]

Closing the issue, feel free to re-open it the above solution didn't work.

[jfbenckhuijsen]

Wel, the thing, is, the property isn't actually required. It's allowed from a functional perspective to be undefined.

[sebelga]

Ok I see. Would setting it as "optional: true" in the Schema be an option then? The validation would still need to be updated.

[jfbenckhuijsen]

optional: true doesn't really change anything. I'm assuming optional: true is the default. Valdation also fails in this case.

[sebelga]

Sorry didn't explain myself well. I was asking your opinion. Do you think that defining the property as "optional" would work from a functional perspective? As having a property with a value of undefined or not being present at all in the data object is the same.
I will then need to update the validation to accept undefined as as valid for properties defined with optional: true. And if some value is passed it will do the validation with the "type" and "validate" setting.

[sebelga]

After giving it a thought there is no need to declare a property as optional if we already have a required setting. I updated the validation and undefined values should validate correctly on properties that are not defined as required.
Will be included in next release. thanks for reporting.

[sebelga]

Closing as v0.7.2 should have fixed it. Let me know if there is still an issue.