RFC: Import and rename decorators from Marshmallow about apiflask

[greyli]

I also think marshmallow.validators is a better module name than marshmallow.validate (that's why I exposed them via apiflask.validators). The one thing I can't easily change is the validate keyword in field classes, if it can be validators, then everything is consistent.

[lafrech]

As for #63, I wouldn't add such a layer for little benefit.

validate vs. validator was discussed in marshmallow-code/marshmallow#645 and this could be reopened if you bring arguments to back up your case.

For pre/post I'd naturally stick to marshmallow's convention, but I understand the will to be close to Flask. There is no best convention. It depends how much you want to expose marshmallow. If you expect users to be familiar with marshmallow, perhaps you should use marshmallow namings. In any case, those names are not expected to change on marshmallow side so your aliases shouldn't break anytime soon.

[greyli]

The pre/post changes are not very necessary. But I do want to change validates/validates_schema to validate/validate_schema, the s is quite redundant for me... Any reasons behind these validates names in Marshmallow, is it just because the validate namespace is occupied by the marshmallow.validate module?

[lafrech]

TBH, I didn't write that and I can only guess.

This is suited as a question / suggestion in our bugtracker. You may link to this issue.

[greyli]

I finally decided to revoke these changes and hope marshmallow-code/marshmallow#1829 would be implemented in the future.