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
We support collection traversal for lists and arrays, so why not maps. Same collectionStrategy semantics would apply. If validating collection members, the validation rule would be passed each Map.Entry as the rule's model. Errors would be registered against the specific map entry.
The map key class will be required to support conversion to/from String using the configured Spring ConversionService. Otherwise, it wouldn't be possible to address the map entries when registering validation errors.
The text was updated successfully, but these errors were encountered:
We support collection traversal for lists and arrays, so why not maps. Same collectionStrategy semantics would apply. If validating collection members, the validation rule would be passed each Map.Entry as the rule's model. Errors would be registered against the specific map entry.
The map key class will be required to support conversion to/from String using the configured Spring ConversionService. Otherwise, it wouldn't be possible to address the map entries when registering validation errors.
The text was updated successfully, but these errors were encountered: