finishedConfigsSubstore
Provides a read-only, consolidated view of all completed configurations. A configuration is considered completed when its status is "completed" (all required elements have selections). This substore aggregates data from configsSubstore, formSubstore, and valuesSubstore into a single, convenient object.
Table of contents
getFinishedConfigs
getFinishedConfigs: (args?: { skipMultiplyConfigQuantity?: boolean;}) => FinishedConfig[]Returns all completed configurations with their ordered steps, selected values, quantities, and products.
Each FinishedConfig is a snapshot combining:
- The
TConfigmetadata (name, quantity, formId, …) - The ordered
stepsarray after constraint evaluation (fromformSubstore) - The current
valuesandquantitiesmaps (fromvaluesSubstore) - The list of
selectedProductsderived from the values
Quantities in each FinishedConfig are multiplied by config.configQuantity by default. Pass skipMultiplyConfigQuantity: true to get raw (un-multiplied) quantities.
type FinishedConfig = { config: TConfig; stepsWithSelections: TStep[]; form: TForm | undefined; values: TValues; quantities: TQuantities; selectedProducts: TProduct[];};Parameters
| Name | Type | Description |
|---|---|---|
args.skipMultiplyConfigQuantity | boolean (optional) | When true, quantities are returned as-is without being multiplied by config.configQuantity. Defaults to false. |
Returns FinishedConfig[] — one entry per config whose status === "completed".
Related
configsSubstore.configs— source ofTConfigmetadata and completion status filterformSubstore.fromConfigs— source ofstepsWithSelections,form, andproductsvaluesSubstore.valuesConfigs— source ofvaluesandquantitiessubmitSubstore.submit— uses similar aggregated data to build the API submission payload