Closed WesTyler closed 7 years ago
Fix is going to be implementing a new entityFor
option: strictInput
, which will default to false to patch the expected behavior above.
Setting strictInput: true
will cause this input validation to occur.
Whether strictInput
is true or false, unknown keys on the input will always be stripped out.
Context
What are you trying to achieve or the steps to reproduce ?
When valid-shaped input with invalid values is provided to a constructor function from Felicity.entityFor, the values should not be stripped out of the input. Only unknown/disallowed keys should be stripped out of the input.
What result did you expect ?
What result did you observe ?