Closed dkellner closed 7 years ago
it's a bug, the same is probably true for schema_registry
.
i'm itchy for a bug-fixing release, @dkellner are you on this issue?
No, I'm not currently working on this and I'm afraid I will not be able to spend time on this the next couple of weeks.
Solved with #294
Used Cerberus version / latest commit: current master (3f673c9527cebc9a4af2ebc5cf4b0ac3e6f4f5d5)
I consulted these documentations:
I consulted these sections of the docs (add more lines as necessary):
[x] I found nothing relevant to my problem in the docs.
[X] I found the documentation not helpful to my problem.
[X] I have the capacity to improve the docs when my problem is solved.
[X] I have the capacity to submit a patch when a bug is identified.
Bug report
Normalization rules like
default
cannot be part of a rules set. Consider these failings tests:The reason is - in my opinion - that the normalization code uses
schema[field]
directly without callingself._resolve_rules_set
where appropriate. This causes other misbehaviour, too:This will fail because code in
__normalize_default_fields
will doschema['bar'].get('nullable', False)
- which will fail becauseschema['bar']
will be the string 'foo'.Is this actually a bug or am I missing something? Are rules sets just meant to be used for validation rules?