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
For now, the extractor only pluck the wanted fields and set the optional to null and the validator just check all required fields are here.
Would it be possible to throw a validation for an extra field is the validated object? Maybe add a allowsExtraFields options, default to true, in the .validate() method?
Or is it already a solution to do that? Thanks
The text was updated successfully, but these errors were encountered:
That said I can sort of see why rejecting extra fields might be desireable when dealing with external data. We had a similar discussion here: haxetink/tink_json#15
For now, the extractor only pluck the wanted fields and set the optional to
null
and the validator just check all required fields are here.Would it be possible to throw a validation for an extra field is the validated object? Maybe add a
allowsExtraFields
options, default to true, in the.validate()
method?Or is it already a solution to do that? Thanks
The text was updated successfully, but these errors were encountered: