You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a copy of the fourth issue collected in #1206 to enable separate tracking of the bug.
The issue
For deep_iterable, only the iterable_validator is optional, which makes sense because if no member_validator was provided, one should simply use a regular validator in the first place. However, for deep_mapping, both value_validator and key_validator are required. This makes its use unnecessarily complicated in certain situations. For example, validating only dictionary keys requires a rather cumbersome workaround and also results in unnecessary calls of the value_validator:
This is a copy of the fourth issue collected in #1206 to enable separate tracking of the bug.
The issue
For
deep_iterable
, only theiterable_validator
is optional, which makes sense because if nomember_validator
was provided, one should simply use a regular validator in the first place. However, fordeep_mapping
, bothvalue_validator
andkey_validator
are required. This makes its use unnecessarily complicated in certain situations. For example, validating only dictionary keys requires a rather cumbersome workaround and also results in unnecessary calls of thevalue_validator
:Instead, I guess the user-friendly way would be to check that at least one of them is provided, but not necessarily both.
The text was updated successfully, but these errors were encountered: