-
-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always set data_key #1864
Comments
I don't have any objection to this right away, assuming it is feasible without too much trouble. It could happen in Anyone willing to work on this? |
@lafrech I'm happy to take look, if you think it can be managed by somebody with no contributions to this project yet. The |
Hello all,
in my application we use and love marshmallow. We have a lot of dynamic coding, therefore we access fields e.g. over the
declared_fields
attribute. Also we need most of the time theField.data_key
attribute which is defined asstr | None
.I would like to suggest an option, which always sets the data_key so that it will never be None. If the user provides it, fine. Else, just set it to the field name. I guess this could also simplify some coding, since you can expect that this attribute is always set.
What do you think?
The text was updated successfully, but these errors were encountered: