null, the instance is created and the caller is expected to retrieve its conditionConfigs from the config property. When assigned, that instance gets conditionConfigs populated and there is no need to get a value from configs property.
This is the value ultimately passed to the ValidationManager config.ValueHostConfigs.
Optional conditionConfig: null | Partial<Omit<RequireTextConditionConfig, "conditionType" | "category">>Optional valueHostName: stringOptional valueHostName: stringOptional ignoreCase: null | booleanOptional conditionConfig: null | Partial<Omit<RegExpConditionConfig, "conditionType" | "category" | "expression" | "expressionAsString" | "ignoreCase">>Optional valueHostName: stringOptional valueHostName: stringOptional conditionConfig: null | Partial<Omit<EqualToValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<EqualToConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<NotEqualToValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<NotEqualToConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<StringLengthConditionConfig, "conditionType" | "category" | "maximum">>Optional valueHostName: stringOptional valueHostName: stringOptional valueHostName: stringOptional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanValueConditionConfig, "conditionType" | "category" | "secondValue">>Optional valueHostName: stringOptional conditionConfig: null | Partial<Omit<LessThanConditionConfig, "conditionType" | "category" | "secondValueHostName">>Optional valueHostName: stringFor 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.
Optional conditionConfig: Omit<RequireTextConditionConfig, "conditionType" | "valueHostName">Optional conditionConfig: Omit<RegExpConditionConfig, "conditionType" | "valueHostName">Generated using TypeDoc v0.25.12
Supports the fluent syntax on conditions that have a single child condition. It isn't an ideal implementation. It is based on using FluentConditionBuilder, which allows a list of conditions. It simply throws an exception if the user atttempts to add more than one condition.
The reason for this implementation is to avoid having the user to register new fluent condition functions in 3 places: FluentValidatorBuilder, FluentConditionBuilder, and FluentOneConditionBuilder. Additionally, they would have to setup their function to return void instead of a FluentConditionBuilder. That is deemed too much work.