When assigned, we can check for naming conflicts.
Protected existingProvides access to services.
If the user needs to abandon this instance, they should use this to clean up active resources (like timers) and to release memory that would stall the garbage collector from disposing this object. It should assign any object reference to undefined as a strong indicator that the object has been disposed.
Add Value Host that does not have direct supporting functions here. This targets ValueHosts without validators. Use the withValidators() function for those.
either the ValueHost name or a ValueHostConfig. When ValueHostConfig, omit the remaining parameters.
Optional arg2: null | string | FluentAnyValueHostParameters<T>optional and can be null. The value for ValueHost.dataType or any additional properties of ValueHostConfig.
Optional arg3: FluentAnyValueHostParameters<T>optional. Any additional properties of a ValueHostConfig.
Completed ValueHostConfig of type T
Protected isFluent format to create a StaticValueHostConfig. This is the start of a fluent series. However, at this time, there are no further items in the series.
the ValueHost name
Optional dataType: null | stringoptional and can be null. The value for ValueHost.dataType.
Optional parameters: FluentStaticParametersoptional. Any additional properties of a StaticValueHostConfig.
Fluent format to create a StaticValueHostConfig. This is the start of a fluent series. However, at this time, there are no further items in the series.
Supply the entire StaticValueHostConfig. This is a special use case. You can omit the valueHostType property.
Fluent format to create a CalcValueHostConfig. This is the start of a fluent series. However, at this time, there are no further items in the series.
the ValueHost name
can be null. The value for ValueHost.dataType.
required. Function callback.
Fluent format to create a CalcValueHostConfig. This is the start of a fluent series. However, at this time, there are no further items in the series.
Supply the entire CalcValueHostConfig. This is a special use case. You can omit the valueHostType property.
Start of a series to collect ConditionConfigs into any condition that implements EvaluateChildConditionResultsConfig. For example:
let fluent = new ValueHostsManagerStartFluent(null);
fluent.input('Field1').all(fluent.conditions().required('Field2').required('Field3'));
The fluent function for allCondition (and others that support EvaluateChildConditionResultsConfig) will get a FluentConditionBuilder whose conditionConfigs collection is fully populated.
Optional config: ConditionWithChildrenBaseConfigWhen null/undefined, 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.
Protected assertHelper for fluent starting nodes to ensure the first parameter supplies a name and that name is not previously defined.
Protected assertGenerated using TypeDoc v0.25.12
Starts a fluent chain for ValueHostsManager. Its methods start CalcValueHost (calc()), and StaticValueHost (static())