-
Notifications
You must be signed in to change notification settings - Fork 238
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
Normalization not working for valueschema and propertyschema #155
Comments
that would work:
but i see that it's not straightforward. normalization of keys can be achieved with a to streamline both, the need to give an empty |
Thank you! This solves my problem for now :). |
funkyfuture
added a commit
to funkyfuture/cerberus
that referenced
this issue
Oct 16, 2015
- 'allow_unknown' and 'purge_unknown' are always considered - normlization of mapping-keys from rules in 'propertyschema' - normlization of mapping-keys from rules in 'valueschema' adresses pyeve#155
funkyfuture
added a commit
to funkyfuture/cerberus
that referenced
this issue
Oct 16, 2015
- 'allow_unknown' and 'purge_unknown' are always considered - normlization of mapping-keys from rules in 'propertyschema' - normlization of mapping-values from rules in 'valueschema' adresses pyeve#155
nicolaiarocci
pushed a commit
that referenced
this issue
Oct 19, 2015
- 'allow_unknown' and 'purge_unknown' are always considered - normlization of mapping-keys from rules in 'propertyschema' - normlization of mapping-values from rules in 'valueschema' adresses #155
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there,
I just stumbled over the following issue: When using 'coerce' in valueschema or propertyschema, validator.document does not get updated accordingly. Consider the following (currently failing) tests:
I don't know whether this is actually meaningful in case of propertyschema. For valueschema, normalization should be possible IMO.
The text was updated successfully, but these errors were encountered: