Email Field validation not working for Schema.dump() about marshmallow

[sloria]

Email and URL fields have built-in "user validators" (stored in each field's validators attribute. User validators are only applied during deserialization, i.e. when calling Schema#load. Schema#dump only validates against field types (e.g. a valid integer is passed to fields.Int).

See #45 (comment) and #47 (comment) for related discussion.

That said, one could argue that the email format validation defines fields.Email's "type" and that it should be validated on serialization. Perhaps this would make fields.Email and fields.URL more consistent with the behavior of the other fields.

[h0st1le]

Thanks for the clarification, the related discussions also helped to better understand the reasoning behind this. That being said I do still like the idea of the fields.Email and fields.URL "type" being used for validation on serialization. As pointed out it would make their behavior more consistent with that of other fields. At the very least maybe an addition to the documentation that points out the current behavior?

[sloria]

I have decided to restore validation upon serialization for Email and URL fields. Thank you for raising the issue!