Optional ValidationGroup child-field setting override

Currently, as of Cx v20.7.1 form fields can override the ValidationGroup settings, e.g. if a ValidationGroup is disabled, the same setting on a respective field, being more specific, overrides it (commit id: c2adf44c9de). In previous versions of Cx it was the other way around, ValidationGroup settings would take precedence over respective field settings within it.

Since both behaviors have valid use-cases, it would be good if the developer could decide which one is more appropriate, via a custom flag, e.g. overrideFieldSettings={true/false} or something in that sense.

The implementation could rely on the optional use of the coalesce function, based on the flag value.

[mstijak]

Strict mode would work in that way that if disabled is evaluated to true on ValidationGroup it would force all children to be disabled. If the value is false, fields can decide for themselves.

The opposite (more common) use-case is that in the non-strict mode the field should able to be enabled by setting disabled to false, ignoring the parent settings, i.e. if one field is an exception.

[mstijak]

Published in cx@20.8.0.