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
allow_unknown
does not apply to sub-dictionaries in a list
#67
Comments
+1 to fix this bug. Maybe "allowed_unknown" should be configurable separately per each scheme like this: schema = {
'a_dict': {
'type': 'dict',
'allowed_unknown': True,
'schema': {
'address': {'type': 'string'},
'city': {'type': 'string', 'required': True}
}
}
} Except for this cerberus is awesome) |
Hey guys, thanks for reporting this one. Should be fixed now. |
@nicolaiarocci , thanks for fix! What do you think about my idea of implement allowed_unknown on schema level? It can be pretty usefull... is it hard to implement? |
Could you open a separate ticket for that? Thanks! |
#40 doesn't seem to apply when the sub-dictionary is in a list.
To reproduce:
On a side-note, cerberus is awesome.
The text was updated successfully, but these errors were encountered: