{
...,
id: {
id: "xxxx",
}
}
- v1.0.0-latest-prod
Now supports Node 18. Node 14 has reached end-of-life and we recommend upgrading to Node 18 as soon as possible since Node 16 reaches end of life in September 2023.
Upgrading Node is not required to use this update.
Added Message component type
Registered Message component in metadata
Added WarningMessage component
Added ability to customize the HelpText icon based on a type.
Added consideration for global errors when evaluating error messages from the request.
This was added to display more specific validation error messages in toast messages on deletion of an entity.
Added ability for MoneyField fields to inherit currency based on the following priority (first being highest) : catalog, entity catalog, application, then tenant.
Added input type mapping for HTML and Money default value fields in the Product Business Type forms
Set maximum width for default value preview display pill and added overflow handling for grouped components that resize due to the default value preview display pills
Added Yup validation methods to be displayed as validation options for Money fields
Added new grid row action for the CSR IMPERSONATE feature.
Previously, this was only available as a secondary entity action.
This action includes a new attribute impersonateSelf that allows a CSR to log into the storefront UI as a Seller rather than as a customer user. Default is false.
This is useful for CSRs managing things like quote requests where they need to access the storefront and aren’t impersonating a customer but as a Seller who must modify and publish a quote.
Added modal size attribute retrieval to apply to modal dialog
Fixed wrong currency symbols displayed on MoneyField fields.
Fixed Offer fields' currency symbols displaying inaccurate currency if a catalog-discriminated entity (e.g. Product) was visited before
Fixed MoneyField fields without an amount value displaying default tenant currency instead of a specified one.
Fixed issue where unsaved form data would reset when an external grid / entity was updated. This was most noticeable when assigning a primary asset to a product.
Fixed how reference ids are stored when using nested content items or other reference type fields (product, category, etc.)
{
...,
id: {
id: "xxxx",
}
}{
...,
id: "xxxx"
}Added buildFilterFromAttributes method to useCollectionState
Supports dynamically building an RSQL string from the following attributes specified in metadata:
targetField
operator
objectPath
objectAttributeKey
This method will search the parent component for the object in the provided objectPath, and map the values found in its respective objectAttributeKey into a string (e.g. id1,id2,id3).
This utility may be used to build RSQL inclusion (=in=) or exclusion (=out=) filters (e.g. targetField=in=(id1,id2,id3))
Added support for metadata conditionals to ColumnHeader and ColumnTypeRenderer
Fixed drag-and-drop functionality for reordering Category Products to be disabled for rows where the related Product is not visible in the current context.
This can happen when a Child Catalog has an inheritance filter that excludes certain Products since the filter targets the Product entity specifically and not the Category Product. (There is a system limitation in the backend preventing that.)
Fixed asset thumbnail placeholder size not matching expected asset size by making it square
Fixed RSQL values stored in fields on entities (like the Category product-inclusion rule) with single quotes (women’s) not being composed and parsed correctly.
Fixed visual bug where the clone product button was not full width
Fixed issue with order item totals incorrectly adding VAT tax to the order item total
Fixed string interpolation mechanism coercing values to strings rather than leaving them as the same type as in the context object
This affected boolean fields when trying to have a default value derived from the value of another field since the type of the value was string instead of the expected boolean causing the wrong option to be selected visually
Fixed default values not being used for boolean fields on Entity Update forms because the fields were mistakenly identified as dirty
Related to this was an issue where after setting the default value the form was again incorrectly identified as dirty
Fixed issue where Fields were not selectable in the Product Type edit field modal
Fixed issue when resolving Sandboxes in the admin
Fixed destructuring error when no backlink attribute was present
In this scenario, return to the previous location