The config that will collect the conditions.
For any implementation of a fluent function that works with FluentConditionBuilder. It takes the parameters passed into that function and assemble the final conditionConfig.
When not null, this will be assigned to conditionConfig for you.
If your fluent function supplies stand-alone parameters that belong in conditionConfig, assign them to conditionConfig.
Generated using TypeDoc v0.25.12
Conditions that use EvaluateChildConditionResultsConfig (All, Any, CountMatches, etc) use this to collect child conditions. This differs from FluentValidatorBuilder as it does not deal with ValidatorConfigs. Yet the same fluent functions are used for both this and FluentValidatorBuilder. As a result, any parameters associated with ValidatorConfig must be optional. Use this when using alternative conditions, as you will need to provide substitutes for each fluent function. Your class should be registered with FluentFactory.