Steven Loria
Steven Loria
thanks for offering to work on this! a pr would be much appreciated
closing for now. further discussion should happen in the linked flask-smorest issue
Ah, i can see how that's confusing. That certainly isn't intentional. PRs welcome!
sorry, can you clarify the ask here? Is it the name of the argument that you're suggesting be changed?
sorry for the confusion. The breaking change refers to the 'validators transform values' alternative, not the proposed approach
on second thought, i don't think field-level pre/post-dump makes as much sense as pre/post-load. field-level transformations are much less common on serialization than in deserialization, and custom fields already address...
I also have medium confidence that `@field_pre/post_load` is unnecessary. the schema-level `@pre/post_load` already provides functionality for doing transformations on one or more fields.
proof of concept of the pre_load and post_load parameters in https://github.com/marshmallow-code/marshmallow/pull/2799
@lafrech i agree that field-level `pre_load` and `post_load` _parameters_ are useful. i was referring specifically to the `@field_pre/post_load` decorator API from my OP; i think that's less useful.
exactly. i've updated the OP to remove the decorator API from consideration