If the business logic provides ValueHostConfigs, they should already be assigned to vmConfig.valueHostsConfig, and the developer will be modifying those configs and adding their own. If the UI is going to create all ValueHostConfigs, vmConfig.valueHostsConfig can be null or []. The user will use the input(), static(), and calc() functions to populate it.
Protected servicesProtected loggerProvides an API for logging, sending entries to the loggerService.
Protected baseProtected overriddenA ValueHostManagerConfig that is getting overridden ValueHost configurations. Each are created by the addOverride() function. They retain a reference to services.
The InstanceState for the ValueHostsManager itself. Its up to you to retain stateful information so that the service works statelessly. It will supply you with the changes to states through the OnInstanceStateChanged property. Whatever it gives you, you supply here to rehydrate the ValueHostsManager with the correct state. If you don't have any state, leave this null or undefined and ValueHostsManager will initialize its state.
The InstanceState for the ValueHostsManager itself. Its up to you to retain stateful information so that the service works statelessly. It will supply you with the changes to states through the OnInstanceStateChanged property. Whatever it gives you, you supply here to rehydrate the ValueHostsManager with the correct state. If you don't have any state, leave this null or undefined and ValueHostsManager will initialize its state.
The state for each ValueHost. The array may not have the same states for all the ValueHostConfigs you are supplying. It will create defaults for those missing and discard those no longer in use.
Its up to you to retain stateful information so that the service works statelessly. It will supply you with the changes to states through the OnValueHostInstanceStateChanged property. Whatever it gives you, you supply here to rehydrate the ValueHostsManager with the correct state. You can also supply the state of an individual ValueHost when using the addValueHost or addOrUpdateValueHost methods. If you don't have any state, leave this null or undefined and ValueHostsManager will initialize its state.
The state for each ValueHost. The array may not have the same states for all the ValueHostConfigs you are supplying. It will create defaults for those missing and discard those no longer in use.
Its up to you to retain stateful information so that the service works statelessly. It will supply you with the changes to states through the OnValueHostInstanceStateChanged property. Whatever it gives you, you supply here to rehydrate the ValueHostsManager with the correct state. You can also supply the state of an individual ValueHost when using the addValueHost or addOrUpdateValueHost methods. If you don't have any state, leave this null or undefined and ValueHostsManager will initialize its state.
Called when any ValueHost had its ValueHostInstanceState changed. React example: React component useState feature retains this value and needs to know when to call the setValueHostInstanceState() with the stateToRetain. You can setup the same callback on individual ValueHosts. Here, it aggregates all ValueHost notifications.
Called when any ValueHost had its ValueHostInstanceState changed. React example: React component useState feature retains this value and needs to know when to call the setValueHostInstanceState() with the stateToRetain. You can setup the same callback on individual ValueHosts. Here, it aggregates all ValueHost notifications.
Called when the ValueHost's Value property has changed. If setup, you can prevent it from being fired with the options parameter of setValue() to avoid round trips where you already know the details. You can setup the same callback on individual ValueHosts. Here, it aggregates all ValueHost notifications.
Called when the ValueHost's Value property has changed. If setup, you can prevent it from being fired with the options parameter of setValue() to avoid round trips where you already know the details. You can setup the same callback on individual ValueHosts. Here, it aggregates all ValueHost notifications.
Called when the InputValueHost's InputValue property has changed. If setup, you can prevent it from being fired with the options parameter of setValue() to avoid round trips where you already know the details. You can setup the same callback on individual InputValueHosts. Here, it aggregates all InputValueHost notifications.
Called when the InputValueHost's InputValue property has changed. If setup, you can prevent it from being fired with the options parameter of setValue() to avoid round trips where you already know the details. You can setup the same callback on individual InputValueHosts. Here, it aggregates all InputValueHost notifications.
Called when the ValueHostsManager's InstanceState has changed. React example: React component useState feature retains this value and needs to know when to call the setState function with the stateToRetain
Called when the ValueHostsManager's InstanceState has changed. React example: React component useState feature retains this value and needs to know when to call the setState function with the stateToRetain
Use this when caching the configuration for a later creation of ValueHostsManager.
Called when the configuration of ValueHosts has been changed, usually through the ValueHostsManagerConfigModifier.apply, or these members of ValueHostsManager: addValueHost, addOrUpdateValueHost, addOrMergeValueHost, discardValueHost. The supplied object is a clone so modifications will not impact the ValueHostsManager.
Note that where a ValueHostConfig has a property that references a function, you will have to retain that reference in some way to reuse it. In particular, ValidatorConfig.conditionCreator.
Use this when caching the configuration for a later creation of ValueHostsManager.
Called when the configuration of ValueHosts has been changed, usually through the ValueHostsManagerConfigModifier.apply, or these members of ValueHostsManager: addValueHost, addOrUpdateValueHost, addOrMergeValueHost, discardValueHost. The supplied object is a clone so modifications will not impact the ValueHostsManager.
Note that where a ValueHostConfig has a property that references a function, you will have to retain that reference in some way to reuse it. In particular, ValidatorConfig.conditionCreator.
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.
Protected assertProtected addProtected destinationExposes the ValueHostsConfig currently capturing content.
Protected applyTrack a new ValueHostConfig in the destinationConfig.
Protected getGets a ValueHostConfig with matching name by looking in previous overrides and the baseConfig. Goal is to find a ValueHostConfig that existed prior to creating the Modifier or using addOverride().
Protected addUtility to use the Fluent system to add a ValueHostConfig to the ValueHostsManagerConfig.
Optional arg2: null | string | Partial<TVHConfig>Optional arg3: Partial<TVHConfig>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.
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.
Same instance for chaining.
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.
the ValueHost name
optional. Any additional properties of a StaticValueHostConfig.
Same instance for chaining.
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.
Same instance for chaining.
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.
Same instance for chaining.
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.
Same instance for chaining.
Protected assertAttaches an enabler Condition to a ValueHost. The Enabler Condition is actually a ConditionConfig object used to create the Condition. This is used to enable or disable the ValueHost based on the condition. If called on a ValueHost already with an enabler, it will replace the existing enabler.
An actual conditionConfig
Using the Builder API
A function that will build the conditionConfig with the Builder API
Protected addFluent format to create any ValueHostConfig based upon ValidatorsValueHostBaseConfig. This is the start of a fluent series. Extend series with validation rules like "required()". Protected because ValueHostManager does not support InputValueHost. ValidationManager offers a public interface.
the ValueHostType to configure
either the ValueHost name for a multiparameter use or InputValueConfig for a single parameter use.
Optional arg2: null | string | Partial<TVHConfig>optional and can be null. The value for ValueHost.dataType or InputValueHostConfig.
Optional arg3: Partial<TVHConfig>optional. Any additional properties of a InputValueHostConfig.
FluentValidatorBuilder for chaining validators to initial InputValueHost
Protected combineCombines a condition with a ValidatorConfig's condition using a rule supplied or callback to let you create a conditionConfig.
The resulting ValidatorConfig's errorCode will not have changed from the original to ensure it aligns with everything depending on the original error code.
the conditionConfig that you want to combine with the new condition.
Either of these:
Optional arg3: ((combiningBuilder) => void)create the condition that you want to combine with the existing condition.
Protected confirmProtected replaceUpdates the conditionConfig property of destinationOfCondition where the replacement is either a conditionConfig or using a Builder object.
If it finds the validator with the errorcode specified, it will replace the condition with the existing condition. If not, it logs and throws an error. If the ValueHost is on an earlier override or baseConfig, a new entry is made in the current override, reflecting the same data as earlier, but now with a modified validator. If the ValueHost is on the current override, the existing entry is modified.
The resulting ValidatorConfig's errorCode will not have changed from the original to ensure it aligns with everything depending on the original error code.
Either of these:
Protected setupReturns a ValueHostConfig that is already in the destinationValueHostConfigs with the desired validatorConfig. If it cannot match both valueHostName and errorCode, it will throw an error.
Protected createSupplies the ValidationManagerStartFluent object, already setup
Generated using TypeDoc v0.25.12
For populating the ValueHostsManagerConfig and ValidationManagerConfig's ValueHostsConfig property using the guidance of functions. Otherwise you would have to define Config objects carefully following their syntax.
instead of