# Changelog All notable changes to `propeller-v2-vue-ui` are documented here. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project aims to follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html) once it reaches 1.0. Until then (the `0.x` line) the public API may change between minor versions; breaking changes are called out below and in [MIGRATION.md](./MIGRATION.md). ## [0.24.0] - 2026-09-25 ### Added - `CartOverviewProps.paymethodLabels` — maps a lowercased payment-method code to its display name, the same contract `CartPaymethods` and `OrderSummary` already use. ### Fixed - **The checkout review step printed the raw payment-method code** (e.g. "Betaling: ON_ACCOUNT") while the step before it showed the method's name for the same selection. `CartOverview` had no way to map the stored code, so it was the one place in checkout where the enum leaked to the customer. Pass `paymethodLabels` to resolve it; it still falls back to the raw value. (PWP-1028) - **The cart line's delete button had no accessible name.** It is icon-only, with no `aria-label`, `title` or visually-hidden text, so assistive technology announced it as just "button". It now carries both, via a `deleteLabel` label key. (PWP-1030) ## [0.23.0] - 2026-09-25 ### Added - `QuickOrderProps.includeTax` and the `colPriceInclVat` label key. ### Fixed - **QuickOrder showed tax-inclusive prices under an "excl. VAT" header, and ignored the shop's price toggle.** The rows read `price.net`, which the API defines as the price *including* tax, while the column said excl. VAT — so a line read 21 % high against the same product on the PDP or in the cart. The component now takes `includeTax` (resolved from the Propeller provider like every other price-bearing component), picks `price.gross` or `price.net` to match, and labels the column accordingly. (PWP-1027) - **The authorization-request detail mixed tax bases in one row.** The unit price came from `totalSum` (excl. VAT) and the line total from `totalSumNet` (incl. VAT), so 1 × € 478,55 showed a € 579,05 total and the lines did not sum to the "Total excl. VAT" figure printed directly below them. Both cells are now excl. VAT, matching that totals block, and the column headers say so. (PWP-1029) ## [0.22.1] - 2026-09-24 ### Fixed - **The language fallback never ran, so a machine listed in one language still opened empty.** 0.22.0 added the fallback but only advanced it on a *thrown* error. The API answers a wrong-language slug with a **partial** response — `machine: null` alongside `SPARE_PARTS_MACHINE_NOT_FOUND_ERROR` — and the SDK's `runOperation` returns that data rather than throwing unless the client opts into `throwOnPartialErrors`, which no boilerplate does. So `getMachine` resolved to `null`, the first candidate language was accepted as a hit, the remaining languages were never tried and `notFound` was never set: one request in the tree language per page, and the same empty listing as before. A `null` machine now counts as "not found in this language" and the loop continues, so the fallback reaches the language the slug was authored in and a slug that resolves nowhere sets `notFound`. (PWP-993) ## [0.22.0] - 2026-09-24 ### Fixed - **An absent boolean prop meant `false`, not "not given" — so the provider was never consulted for VAT.** `defineProps<{ includeTax?: boolean }>()` compiles to `{ type: Boolean }`, and Vue casts an absent `Boolean` prop to `false` rather than leaving it `undefined`. `useInfraProps` asked `props[key] !== undefined`, saw that phantom `false`, treated it as an explicit override and skipped `` entirely. A shop configured for incl-VAT prices rendered **every** price excl. VAT unless each host passed `includeTax` by hand — on `ProductPrice`, `ProductCard`, `ProductGrid`, `ProductSlider`, `ProductBulkPrices`, `ProductBundles`, `ProductInfo`, `SearchBar`, `CartItem`, `ClusterCard`, `AddToCart`, `CartBonusItems`, `FavoriteListDetails`, `FavoriteListItem` and `ItemsOverview`. `useInfraProps` now asks the component instance what the parent actually passed (`vnode.props`, which is pre-cast), so the question it answers is "did the host set this?" rather than "is this defined?". String keys (`language`, `currency`) were never affected — which is why the locale fix held while VAT kept coming back. Fixed in one place, so it covers every boolean infra key including ones added later. Explicit props still win, and a kebab-cased attribute (`:include-tax`) counts as explicit. - **Boolean props documented as defaulting to `true` defaulted to `false`.** The same cast, reached a different way: `showStock ?? true` can never see `undefined`, so the `?? true` was dead code. - `MachineGrid` — stock, prices, add-to-cart and cart creation were all off unless passed, while the React twin had them on. This is the parity gap reported against 0.20.0. (PWP-995) - `ProductBundles.showIndividualItems` — bundle contents were never listed. - `ProductBundles.showLoginPrompt`, `ProductPrice.showLoginPrompt` — the "log in to see prices" prompt never rendered. - `ProductCard.allowIncrDecr`, `ProductSlider.allowAddToCart`. - `PriceToggle` — `value` is the controlled/uncontrolled sentinel, so the cast pinned the toggle in controlled mode: an uncontrolled toggle sat at "excl. VAT" and ignored its own clicks. `initialState` was affected too. - `ProductGrid.applyOrderlists`, `SearchBar.applyOrderlists`, `QuickOrder.applyOrderlists` — downstream reads `=== false` as "the host deliberately disabled orderlist scoping", so contract scoping was silently off on every listing that did not pass it. `scripts/check-boolean-defaults.mjs` (`npm run check:props`, also wired into `prepublishOnly`) now fails the build when a prop's doc comment promises a `true` default that the compiled component does not carry. The doc comment is the spec; nothing needs updating when a component is added. - **A machine listed in one language could not be opened.** 0.20.0 stopped the listing from narrowing to a single language, so an NL-only installation appears in an EN tree and is linked by its NL slug — but `machine(slug:)` resolves a slug **only** in the language it was authored in, so following that link asked for `machine(slug: "", language: "EN")` and got `SPARE_PARTS_MACHINE_NOT_FOUND_ERROR`. The page then showed a title derived from the slug, no parts and no error: the bug moved one click deeper instead of going away. `useSpareParts` now tries the tree language, then the storefront language, then any locales given in the new `machineLanguages` option, and upper-cases each (the API matches case exactly — `nl` misses where `NL` hits). A slug that resolves in none of them sets the new `notFound` flag, and `MachineGrid` renders "This machine could not be found." instead of an empty listing. A fully-translated shop still costs exactly one request. (PWP-993) - **"Qty in machine" and "Search parts…" stayed English in a translated shop.** Both were read from `toolbarLabels`, which is forwarded verbatim to `GridToolbar` — so they belonged to no toolbar dictionary, and a shop that translated its `GridToolbar` keys properly still got English. They now come from `machineCardLabels` (the grid's own label bag, alongside `loading`, `noMachines` and the new `machineNotFound`), falling back to `toolbarLabels` so hosts that already set them keep working. (PWP-995a) ### Added - `MachineGrid.machineLanguages` / `useSpareParts.machineLanguages` — the locales to try when a machine slug does not resolve in the tree language. - `useSpareParts().notFound` — the slug resolved in none of the candidate languages, as distinct from "resolved but has no parts". - `machineCardLabels.machineNotFound` — copy for that state. ## [0.21.0] - 2026-09-24 ### Fixed - **Media language is matched case-insensitively.** The API lowercases `documents[].language` while leaving `alt[].language` as uploaded, so `ProductDownloads` matched the label but never the file and served `documents[0]` — the Dutch PDF under an English label. `ProductVideos` had the identical comparison and worked only by data luck. Also fixed in `useProductSearch.filterByLanguage`, where a case mismatch dropped **every** product from the grid, and in `DefaultProductImage`. (PWP-984) - **`checkoutAllowed` is usable, and fails closed.** It read the raw `companyId` option rather than the resolved one, so a contact acting for their own company matched no authorization config and every cart reported as within limit; and it evaluated its own cart state, which stays null when the consumer only seeds a `cartId`. The hook now hydrates a seeded cart, and reports `false` while that is in flight rather than `true`. (PWP-988) - **The place-order button is gated on the authorization limit.** An over-limit purchaser opening checkout directly got an ungated button and a backend rejection; `CartOverview` now shows an `authorizationRequired` message instead, using the same predicate as the cart summary. (PWP-988) - **Semi-closed surfaces no longer flash their logged-out state** for a signed-in visitor while the profile loads. Every `isContentHidden` call site passes the provider’s `isAuthenticated` (core-ui 0.9.0+). (PWP-989) - **The cart sidebar slides again.** The overflow fix named only `transform` in its transition, but Tailwind v4 emits `translate-x-*` as the `translate` property, so the panel jumped. (PWP-1002) - **Header triggers inherit their colour.** `AccountIconAndMenu` and `CompanySwitcher` hardcoded `text-white`, which broke light headers; `text-foreground` then broke dark ones. Both now use `text-inherit`, with the hover tint derived from `currentColor`. (PWP-1005) ### Added - `CompanySwitcher` accepts `triggerClassName`; it had no class prop at all. - `ProductInfo` accepts `cartId`, `createCart` and `onCartCreated`, and forwards them to both the injected and the default add-to-cart. It declared none of them, so the PDP’s add-to-cart always failed for a visitor without a cart. `ProductCard` forwards the same to an injected component. (PWP-986) - `CartOverview` resolves `user` and `companyId` from `PropellerProvider`. ## [0.20.0] - 2026-09-23 `MachineGrid` stops losing rows, and becomes usable in a translated or customised storefront. One project had given up on it and rebuilt the equivalent surface by hand, losing the breadcrumb, module grid and filter wiring. ### Fixed - **A machine with no slug in the tree language is no longer dropped from the list.** `childSlugHref` returned `null` and the card was filtered out, so a customer saw three of four machines with nothing saying so — and the same helper guards the child-module grid, so a module could vanish from a machine the same way. Two changes: `ROOT_MACHINE_FIELDS` no longer passes `(language: $language)` to `name` / `description` / `slug`, so the cross-language fallback in `getLocalizedValue` has entries to fall back to; and a machine with no slug in *any* language now renders as an unlinked card rather than vanishing. Needs SDK ≥ 0.17.0 for the child-machine half, which comes through `getMachine`. (PWP-993) The asymmetry that made this hard to spot: the **name** falls back across languages, the **slug** did not — so a half-translated tree rendered names in the wrong language rather than failing, but lost whole rows when the slug was the missing half. ### Added - **`MachineGrid` forwards label overrides to the parts list.** It rendered its parts through `ProductGrid` but forwarded none of `productCardLabels`, `addToCartLabels`, `stockLabels`, `priceLabels` or `labels`, and there was no way to reach them from outside — so "In stock", "Add" and "Search parts…" appeared in English in the middle of translated copy. A monolingual shop never noticed. (PWP-995a) - **`MachineGrid.productCardComponent`** — the `ProductGrid` prop of the same name, forwarded. Without it a quote-only product rendered with the host's custom card on a normal listing and with the stock card inside a machine, so the same product looked different depending on the page it was reached from. (PWP-995c) - **`useSpareParts({ page })`** — a controlled page `Ref`, mirroring the existing controlled `parts` — pass a `Ref`. Every other listing input (`term`, `textFilters`, `sortField`, `pageSize`) was already an option, so the absence of `page` read as "paging is internal" — and it was not: driving the hook from URL state and rendering `` changed the URL and re-rendered the same first twelve parts. The only way in was a `watch(() => listing.page, goToPage)` that `MachineGrid` did internally and nothing documented. `goToPage` still works for uncontrolled hosts; omit `page` for the previous behaviour. (PWP-995b) ### Changed - `MachineCard.href` is now optional — a machine with no URL renders as a `
` instead of an ``. - **`MachineGrid` drives `useSpareParts` with `page` directly** instead of the internal `goToPage` watcher. ### Documentation - **`MachineCardProps.labels` documented one key while `MachineGrid` read three.** The doc named only `viewMachine`; `MachineGrid` also reads `loading` and `noMachines` off the same object, so anyone following the doc left those two in English. Both sides now say so. (PWP-995d) ## [0.19.0] - 2026-09-21 ### Fixed - `FavoriteListDetails` and `useCart.getCrossupsells` priced items for the contact's default company instead of the company selected in the switcher, so a multi-company contact saw the wrong prices while the cart charged the selected company's. Both now resolve the active company as `companyId ?? user.company.companyId`, matching `useProductSlider`. - `CartItem` never passed `companyId` into `useCart`, which also left `checkoutAllowed` skipping the PAC authorization-limit check and `fetchActiveCart` unfiltered by company. - `FavoriteListDetails` and `CartItem` fetched only on mount, leaving stale prices on screen after a company switch. Both now re-fetch when `companyId` changes. - The closed `CartIconAndSidebar` panel widened the document by its own content width (~128px once the cart had items), giving signed-in users a stray horizontal scrollbar. A transform does not remove an element from scrollable overflow, so the parked drawer is now `visibility: hidden` while closed. (PWP-1002) - `ProductDescription`, `ProductShortDescription`, `CategoryDescription` and `CategoryShortDescription` emitted Tailwind Typography `prose` classes, but the plugin is installed neither here nor in the consuming apps — so the classes compiled to nothing while this package's own Preflight stripped list markers, and bullet lists rendered as bare lines. The four surfaces now carry real styling in `dist/styles.css`, with no consumer plugin required. (PWP-1000) - `ItemStock` rendered `(120pcs)` with no separator between the count and the unit label. (PWP-1005a) - `OrderList` filter labels carried Tailwind's `capitalize`, which title-cases every word and mangled translated labels ("Terme De Recherche", "Aangemaakt Op"). The dictionaries already carry the right casing. (PWP-1005b) - `AccountIconAndMenu` hardcoded a dark-header scheme (`text-white`, `hover:bg-white/10`) that rendered white-on-light, and styled its active sidebar link with the `secondary` ramp where every other selected surface in the package uses `primary`. Both now use theme tokens. (PWP-1005c) ### Added - `FavoriteListDetails` accepts a `companyId` prop, resolved from `PropellerProvider` when omitted. - The purchase-authorization rule existed in three divergent copies — `useCart`, `CartSummary` and `CartIconAndSidebar` each re-implemented the PAC lookup with their own field-tolerant reads. All three now call `isOverAuthorizationLimit` from core-ui, which absorbed the underscore-shape handling so it covers both packages. This also fixes `useCart.checkoutAllowed` failing open: it returned `true` when the composable's own cart was null, which it is until the consumer calls `addItem`/`resolveCart`. `CartSummary` carried a comment recording that this had put "Continue to Checkout" up in CartView for a user over their limit. (PWP-988) ### Changed - `ProductDownloads.downloads` and `ProductVideos.videos` are now nullable as well as optional, matching what the API actually returns — it answers `null`, not an empty page, when a product has no documents or videos. (PWP-1009) - `GridPagination.products` is now structural (`{ page, pages }`) instead of a full `ProductsResponse`. A real response still fits; callers holding the two numbers on their own no longer need a cast. (PWP-1005e) - **Breaking (types):** `GridToolbar.viewMode` and `onViewChange` are narrowed from `string` to `'grid' | 'list'`, matching their documented contract. A consumer passing a plain `string` will need a cast or a narrower type. (PWP-1005d) ## [0.18.2] - 2026-08-27 The Vue half of the fix shipped in react-ui 0.19.2, so the two surfaces stay in step. ### Fixed - **Money formatted at the Dutch default wherever the host didn't pass `language`.** `localeForLanguage(undefined)` is `nl-NL`, so a component that reads `props.language` straight off its props prints Dutch separators unless every host remembers to thread the prop. `ProductCard` resolved it from the provider; several others did not, so one English page could show `€ 1,42` in its PDP hero price and `€1.70` on the cards beneath it. - `ProductPrice` and `ProductBulkPrices` now resolve their infra through `useInfraProps` like the rest of the package, so `language`, `currency`, `includeTax`, `user` and `portalMode` all come from `` unless the host overrides them. - `CartItem` declared `language` and `currency` in its `RESOLVE_SPEC` and then formatted every price off `props.*`, so that resolution was dead code for exactly those keys. Its money and localized names now read the resolved values. ## [0.18.1] - 2026-08-26 The Vue half of the fix shipped in react-ui 0.19.1, so the two surfaces stay in step. ### Fixed - **Order and quote lines whose product is gone from the catalog.** A product that is hidden, withdrawn or deleted still appears on every order and quote it was sold on, but the API returns no product record for it — `orderItem.product` is simply absent. `OrderItemCard` already fell back to the order item's own snapshot of the line for the name, sku, thumbnail and link, but not for the price: an injected `priceComponent` was handed `product.price`, rendered blank on `undefined`, and the line total silently disappeared from the row. Such a line now falls through to the order item's `priceTotal`. Rows with a product are unaffected — the slot is still used whenever there is a catalog price to give it. - **`OrderShipments` printed `-` for the SKU** of a shipment line whose product is missing, having read `product.sku` with no fallback. It now reads the order item's own `sku`, which is stored on the order and always there. ### Internal - Vitest now compiles SFCs (`@vitejs/plugin-vue`, already a dev dependency), so pure display components can be asserted on through `vue/server-renderer` without jsdom or a provider wrapper. Component tests that need a mock SDK stay out of scope here, as before. ## [0.18.0] - 2026-08-26 The Vue half of the storefront-integration batch shipped in react-ui 0.19.0, so the two surfaces stay in step. ### Added - **`useCart().addItems(items)`** — sequential bulk add that threads each add's resolved cart id into the next. "Add this whole set to the basket" is a normal requirement (kits, re-order, recipe packs) and there was no bulk call, so every consumer wrote the loop themselves. - **Bonus items in the add-to-cart modal.** A promotion granting a free product said nothing at the moment it fired; the shopper only found it by opening the cart later, which is after it can influence them. Only the items *this* add earned are shown. `bonusItemsLabels` overrides the block's labels. - **`className` on `CartSummaryProps`**, and `currency` on `GridFiltersProps` / `GridToolbarProps`, resolved from `` when omitted. - **`language` on `ProductBulkPricesProps` / `ProductPriceProps`**, which decides the number format prices render in. ### Fixed - **Prices used Dutch separators in every language.** Every caller passed only a symbol and left `formatPrice`'s locale at its `nl-NL` default, so an English shop rendered `£ 3,45`. Number format now follows the storefront language via core-ui's `localeForLanguage`, giving `£3.45`. Dutch output is unchanged. - **The price-range inputs and the active price-filter chip hardcoded `€`.** The chip had neither a prop nor a class, so no userland fix existed. - **`ProductBulkPrices` ignored an explicit empty `title`.** The heading is resolved with `getLabel`, which treats `''` as missing and substitutes its English default — so the component's own "no title, no heading" branch was dead code and the block rendered "Volume pricing" on a Dutch page. - **The mini-cart labelled an excl-VAT figure "Total".** The cart page calls the same number "Total excl. VAT" and reserves "Total" for the incl-VAT figure, so the first number a shopper saw understated the price by one VAT amount. The label now follows the same switch the figure does (new key: `totalExclVat`). - **`CartSummary` painted a card background with no card** — no padding, radius or shadow, directly above a properly styled `ActionCode` in the same column. - **`SearchBar`'s input was styled for a dark header** (`bg-white/95 border-white/20`), rendering as a white-on-white ghost on a light one. It now uses the themed surface and border tokens. - **Order-item links dropped the locale prefix.** `OrderItemCard` built `/product/:id/:slug` from literals instead of the host's URL builders, so on a prefixed storefront the link sent the visitor to the default language. It now uses `configuration.urls` when supplied, with the literals as a fallback. (`SearchBar` already did this correctly.) - **`OrderList` showed a bare line of text while loading**, collapsing the list and snapping it back — most visible when switching language on the account pages. It renders skeleton rows that hold the layout instead. ### Changed - Requires `@propeller-commerce/propeller-v2-core-ui` `^0.7.0`. ## [0.17.0] - 2026-08-21 ### Added - **After-hooks now say WHAT happened, not just that something did.** Three callbacks reported success with no argument, which made them unusable for anything that has to distinguish the outcome — analytics, audit trails, or optimistic UI. All three arguments are optional, so existing zero-argument callbacks keep working unchanged. Brings the package level with `propeller-v2-react-ui` 0.18.0, which shipped the same three. - `AddToFavorite.onFavoriteChanged(change?)` — `{ action: 'added' | 'removed', listId, productId, clusterId }`. It fired identically for an add and a removal, so a host could not report "added to wishlist" without inventing the direction, and a wishlist metric that also counts removals is worse than no metric. - `FavoriteLists.onListChanged(change?)` / `useFavorites` — `{ action: 'created' | 'updated' | 'deleted', listId, name, isDefault }`. Note the existing `onCreate` / `onEdit` / `onDelete` props are *overrides* that replace the default mutation, so they were never usable as notifications. - `QuickOrder.onTemplateDownload()` — the template link was a bare ``, so a buyer fetching the spreadsheet left no trace. Navigation is untouched. ### Notes - The add payload captures the selected list id *before* the ref is cleared. The React twin reads the pre-update value out of its closure after `setState`; a Vue ref updates in place, so the same code there would report an empty `listId`. - `QuoteActions` deliberately gains no `afterReject`: the component has no reject action to hook — only accept. A rejection callback would be dead API. - `PurchaseAuthorizationRequests` needs no new prop either; the existing `afterDeleteRequest` already covers the manager rejecting a request, which is what "delete" means in that UI. ## [0.16.0] - 2026-08-20 ### Fixed - **A host `*ClassName` override could not beat the component's own utility .** Class lists were built by string-appending the override after the package's defaults, which decides nothing — the cascade does, not attribute order. `iconClassName="text-cocoa"` on `AccountIconAndMenu` (baked-in `text-white`) produced an element carrying both and rendered white. The four override sites (`iconClassName`, `menuClassName`, `sidebarClassName`) now merge through `tailwind-merge`, so a conflicting utility is replaced rather than raced. BEM hooks and non-conflicting utilities are untouched. - **Anonymous catalog listings were scoped differently on the client than on the server.** Listing composables derived `userId` only from a logged-in user and omitted the key entirely for guests, while a server-side seed scopes anonymous queries to the channel's `anonymousUserId`. The two asked different questions, so the client refetch quietly replaced a correctly-scoped product list with a differently-scoped one — assortment rules, negative order lists in particular, are applied per user. All four listing composables (`useProductSearch` ×2, `useProductSlider`, `useQuickOrder`, `useSpareParts`) now resolve the id through one shared helper. Hosts that supply no `anonymousUserId` behave exactly as before. ### Added - **`configuration.anonymousUserId`** — the channel's guest account, resolved server-side and handed to the package so client-side listings scope to it. Same route `baseCategoryId` takes; no module guesses it. ## [0.15.0] - 2026-08-12 ### Fixed - **Result and order-item links used default-language slugs.** Vue already resolved localized *names* by language everywhere; the *slugs* that build URLs did not. `OrderItemCard` (product and cluster link) and `SearchBar` (autosuggest result link) read `slugs[0]`, which is the catalog's default language, so every non-default locale emitted wrong-language links — a link-correctness and SEO problem rather than a cosmetic one. Both now use `getLanguageString` with the active language, matching the names beside them. - **`useCart` never adopted a cart id that arrived after setup.** `ref(unref(options.cartId) || '')` unwrapped the caller's id once, so a component created before the cart resolved held `''` permanently — even when the host passed a `Ref`. The header's cart sidebar renders on the first paint of every page, so its "Request authorization" button rendered enabled, fired, and returned `err('No cart')` with nothing sent. `cartId` is now a computed over the caller's value, so a `Ref` stays reactive and a plain string still works. `processCart` was affected the same way. ### Changed - The favorites list's add-product button default now reads "Add product to favorite list" instead of "Add product directly to this wishlist". Hosts that translate `FavoriteListDetails.addProductDirectly` should update their own copy — "favorite list" is the agreed term, not "wishlist". ## [0.14.10] - 2026-08-11 ### Fixed - **Checkout step 3 opened with nothing selected on a fresh cart.** `CartPaymethods` and `CartCarriers` only ever adopted a value the cart already stored, so a cart that had never reached step 3 — every first order, and every order after the cart is recreated — rendered both grids blank and refused to continue until the user clicked. They now preselect the cart's stored option when there is one and otherwise the first option offered. Mirrors React 0.15.11. - **"On account" was never hidden from guests.** `CartPaymethods` compared the `showOnAccountForGuests` / `isGuest` *computed refs* instead of their `.value`, and a ref object is always truthy, so the guest filter never ran. It would also have won the new preselection. ### Changed - The active option is now derived from the cart rather than assigned by a watcher, so it is present in the first render instead of appearing after mount. The upward notification moved off an `immediate` watch onto `onMounted`, so it no longer fires during SSR — where a host that persists the choice would have mutated the cart while rendering. ## [0.14.9] - 2026-08-11 ### Fixed - **The cart sidebar's "Bonus items" heading stayed English on a localized page.** `CartIconAndSidebar` renders `CartBonusItems` itself but passed it no `labels`, so the block always fell back to its English defaults — while the same component on the cart and checkout pages, where the host passes `labels` directly, translated correctly. Mirrors React 0.15.10. ### Added - `CartIconAndSidebar` accepts `cartBonusItemsLabels` (keys: `title`, `sku`), forwarded to the embedded bonus-items block. Hosts already translating `CartBonusItems` on the cart page can pass the same map. ## [0.14.8] - 2026-08-11 ### Fixed - **Quick order could add products from outside the user's catalogue.** Both the row typeahead and the XLSX upload resolved codes through the flat `products` resolver with no catalog scope and no user context. Orderlist (contract) scoping is honoured by `category.products` but **silently ignored** on the flat resolver, so quick order surfaced the full catalogue while the grid and the search preview stayed scoped. `searchProducts` now queries `category.getCategory` over `configuration.baseCategoryId` and passes `userId` / `companyId` / `applyOrderlists`, plus `hidden: false`, matching `ProductGrid`, the SearchBar and the WordPress plugin's quick-order flow. Codes outside the catalogue are reported through `onMissingCodes` instead of being added. Mirrors React 0.15.8. ### Changed - **`QuickOrder` needs `configuration.baseCategoryId`.** Without it the typeahead and the upload resolve nothing rather than falling back to an unscoped search — failing closed is the point of the fix. ### Added - `QuickOrder` accepts `taxZone` (defaults to `'NL'`), `orderlistIds` and `applyOrderlists`, forwarded to the scoped search. ## [0.14.7] - 2026-08-10 ### Fixed - **`OrderBonusItems` showed the list price of a free item.** The API models a bonus as two order lines: the product line at its list price, plus a sibling `class: 'incentive'` line carrying the negative delta and pointing back via `parentOrderItemId`. The component rendered the product line and ignored the sibling, so a bonus that reads € 0,00 in the cart and at checkout reappeared at its list price on the thank-you page and in order details. Bonus lines are now netted against their incentive siblings via `getNettedBonusItems()` (core-ui 0.6.2); partial discounts keep their remainder instead of collapsing to zero. Order totals were already correct — this was display-only. ## [0.14.6] - 2026-08-10 ### Fixed - **User-visible strings that could not be translated at all** — they had no label key and no prop, so a consumer supplying a full `labels` dictionary still shipped English on a Dutch page. Every one now resolves through `getLabel` with the previous text as the fallback, so this is additive: a consumer supplying none of the new keys renders exactly as before. | Component | Was | New key | |---|---|---| | `CategoryDescription` | Read more / Read less | `readMore`, `readLess` | | `ProductDescription` | Read more / Read less | `readMore`, `readLess` | | `MachineGrid` | Loading…, No machines found. | `loading`, `noMachines` | | `RegisterForm` | Please select an account type. | `selectUserType` | | `AccountIconAndMenu` | Hi, {name} | `greeting` | `ProductTabs` now forwards its `labels` to `ProductDescription`, without which the two new keys could not be reached on a product page. The greeting takes a `{name}` placeholder rather than a bare prefix, so a translation can put the name first — matching the existing `{link}` convention in `LoginForm.noAccount`. - **The add-contact server error is overridable.** `PurchaseAuthorizationConfigurator` rendered the failure verbatim — unlocalised upstream text, often cryptic. Supplying `addContactFailed` now replaces it outright, the same masking `LoginForm` already does with `invalidCredentials`. Omit the key to keep the current pass-through. - **Both authorization modal close buttons had no accessible name.** The `✕` glyph and the SVG icon were the only content, so screen readers announced punctuation or nothing. Both take an `aria-label` from the existing `closeLabel` key, with the glyph/icon marked `aria-hidden`. Matches `propeller-v2-react-ui` 0.15.6, except `registrationFailed` — this package's `RegisterForm` does not render raw server errors. ## [0.14.5] - 2026-08-10 ### Fixed - `useMenu` no longer drops categories that lack a translation in the active language. The query filtered server-side — `names(language: $language)` — so a category with no entry for that language came back with `names: []` and `slugs: []`, and `mapCategory`'s fallback had nothing left to fall back to: the row rendered with a blank label and an empty slug, invisible and unclickable. Switching a bilingual storefront to a language with partial translations collapsed the menu to whichever categories were translated . `names` and `slugs` are now fetched unfiltered and `mapCategory` picks the active language, falling back to whichever translation exists. Matches `propeller-v2-react-ui` 0.15.5. ## [0.14.4] - 2026-08-10 ### Fixed - `` follows the Incl./Excl. BTW toggle. It printed `item.price × quantity` — always excl. VAT — while `` on the cart page printed `totalSumNet` (incl.), so the same lines appeared on two different tax bases in consecutive checkout steps. It now reads `includeTax` from the Propeller provider and takes line totals from `totalSum` / `totalSumNet` — the same fields `` reads. Bundle, bundle-item and child-option prices switch on the same basis. Hosts that already render inside `PropellerProvider` need no change; pass `includeTax` explicitly to override. Matches `propeller-v2-react-ui` 0.15.4. ## [0.14.3] - 2026-08-10 ### Fixed - `` renders a **Transaction costs** line when the cart's payment method carries a fee. The fee was already inside `total.totalGross`, so the panel's own rows never added up to the "Total excl. VAT" it printed — a €7.25 order with €49.00 shipping showed €56.60. `` has always shown this row; the cart panel now matches. Label key: `transactionCosts`. Matches `propeller-v2-react-ui` 0.15.3. ## [0.14.2] - 2026-08-10 ### Fixed - `` resolves each facet's label in the active language. The title came from `descriptions[0]`, so on a bilingual tenant every filter heading rendered in whichever language the API returned first (Dutch), regardless of the shopper's selection. It now matches on the `language` prop, falling back to the first description and then the raw attribute name. Hosts must pass `language` to `` / `` for the labels to follow the language switcher; omitting it preserves the previous behaviour. Matches `propeller-v2-react-ui` 0.15.2. ## [0.14.1] - 2026-08-10 ### Fixed - `` shows an unticked option its **own** result total instead of the intersection with the group's active selection. Once a group held a selection the backend's `count` for a sibling became "products carrying both values" — a season facet read "(1)" and added 2 products when ticked. The count now comes from `countActive` (the option with its own group's filters lifted, other groups still applied), which is what the field is documented for. With no selection in the group the backend returns `count === countActive`, so unfiltered listings are unchanged. Mirrors react-ui 0.15.1. ## [0.14.0] - 2026-08-07 ### Fixed - **Checkout is operable by keyboard and screen reader.** ``, `` and `` rendered their options as plain `div`s with a click handler: no `input[type=radio]` anywhere, no roles, not focusable, and an empty accessibility tree for the checkout body. Because choosing a carrier is required to advance, keyboard-only and screen-reader users could not complete an order at all. The three now implement the ARIA radiogroup pattern — the grid is a `role="radiogroup"` with an `aria-label`, each option is a `role="radio"` carrying `aria-checked`, and a roving `tabindex` makes the group a single tab stop. Enter/Space select; arrow keys move and select with wrap-around. Options also gained a `focus-visible` ring, since a keyboard user has to be able to see where they are. The markup and styling are otherwise unchanged. New optional label keys, each with an English fallback: `methodsLabel` (CartPaymethods), `carriersLabel` (CartCarriers), `deliveryDateLabel` (DeliveryDate) — they name the group for assistive tech. - **Product names respect the active language.** Fifteen call sites across eight components read `names[0].value` — whichever translation the backend happened to return first. On a Dutch storefront that surfaced German product names on the checkout review and thank-you screens while the cart showed the Dutch one. They now resolve through `getLanguageString(names, language)`, which falls back to the first non-empty entry, so behaviour is unchanged wherever the active language was already first. Affects ``, ``, ``, ``, ``, ``, `` and ``. ### Added - `` accepts `language` (resolved from `` when omitted). It previously had no language input at all, which is why the thank-you page could not localize its item names. ### Changed - Built against `@propeller-commerce/propeller-v2-core-ui` **0.6.1** (the ENUM cluster-configurator fix). The declared range `^0.6.0` is unchanged; only the lockfile moved. The package's own `node_modules` had drifted to core-ui 0.4.0, which made `typecheck` fail on exports that 0.6.x does provide. ## [0.13.0] - 2026-08-06 ### Changed - **BREAKING — the stock filter is a toggle plus a quantity, not two checkboxes.** `` now takes `activeAvailability` as a single `Availability` (`'all' | 'in-stock'`) rather than an array, gains `activeMinStock`, and its `onAvailabilityChange` fires with both the selection and the quantity. `` takes `availability` as a single value plus `minStock`, and its `onAvailabilityFilterRemove` takes no argument. `` takes `availability` plus `minStock`. The out-of-stock bucket has no replacement. See [MIGRATION.md](./MIGRATION.md). Two checkboxes could express "in stock or out of stock" — every product, and so a state that looked active but sent no filter. They also could not answer what a shopper asks next: not "is it stocked?" but "do you have enough?". The section is now a two-state toggle and, once In stock is chosen, an editable quantity with stepper buttons. The value can be typed directly or stepped, commits on blur or Enter, and is floored and clamped to a minimum of 1 — a lower threshold would match zero-stock products and contradict the toggle. Switching back to All products clears it. Requires `propeller-v2-core-ui` >= 0.6.0. - **The toolbar shows one stock chip** instead of one per bucket, carrying the quantity when it is above the default. ### Added - Label keys `allProducts`, `atLeast`, `pcs`, `quantityDecrease` and `quantityIncrease`. The `outOfStock` key is no longer read. Matches `propeller-v2-react-ui` 0.15.0. ## [0.12.0] - 2026-08-05 ### Added - **`hideHeader` and `flat` on `` and ``** — for embedding a list inside a host's own card. `hideHeader` drops the table's column-header row, redundant once a card names what it contains and shows three columns. `flat` drops the component's own background, border, shadow and rounded corners, which otherwise nest a box inside the host's box. On `` the empty state honours `flat` too, so a card with no results does not draw a stray panel. - **`limit`, `columns`, `columnConfig`, `showActions` and `hideTitle` on ``** — the component rendered a fixed five-column table (date, quantity, total, requested by, actions) and its own heading, so it could not be reduced to a summary. `columns` selects which of those render and in what order, `columnConfig` overrides their header labels, `showActions` hides the accept/delete buttons, `hideTitle` suppresses the component's own heading when the host already has one, and `limit` caps the list to the most recently modified — mirroring the prop `` already carries. ### Notes Every prop above is additive and defaults to current behaviour: an existing consumer that passes none of them renders exactly as it did in 0.11.0. In particular `` still lists requests in the order the API returned them; the most-recent-first sort applies only when `limit` is set, so the rows that survive the slice are the newest. Matches `propeller-v2-react-ui` 0.14.0. ## [0.11.0] - 2026-08-05 ### Added - **Availability filter on ``** — an opt-in section below the price block with two checkboxes, In stock and Out of stock, wired to the server-side stock filter the SDK exposes on `CategoryProductSearchInput`. New props: `showAvailabilityFilter` (defaults `false`), `activeAvailability` and `onAvailabilityChange`. Nothing selected sends no filter, so the default listing is unchanged. Selecting both buckets means "in stock or out of stock", which is every product. The filter has no OR operator and the union is the unfiltered set anyway, so both-selected sends no filter — the same as selecting neither. The checkboxes stay ticked; only the request collapses. The mapping lives in `propeller-v2-core-ui`'s `buildInventoryFilter`, so this package never restates the operator semantics. Requires `propeller-v2-core-ui` >= 0.5.0 and `propeller-sdk-v2` >= 0.15.0, where the inventory filter was added. - **`availability` and `onAvailabilityFilterRemove` on ``** — the active-filter row now renders one removable chip per selected bucket, so a stock-filtered listing shows why its results are narrowed and can be undone from the results area. One chip per bucket, matching the attribute chips rather than the price chip which covers a whole range. The row's active check accounts for availability, so it appears when availability is the only active filter. - **`availability` on ``** — forwards the selection to `useProductSearch`, which applies it to both the grid fetch and the typeahead preview. Filtering only the grid would let the preview offer products the grid then hides. ### Changed - The availability section is hidden for anonymous visitors in a semi-closed portal, the same rule the price filter already follows. Hosts should pass their own "show stock" setting through `showAvailabilityFilter`: filtering by stock reads as broken when the cards display no stock to filter on. Matches `propeller-v2-react-ui` 0.13.0. ## [0.10.0] - 2026-07-31 ### Added - **`productTrackAttributes` on ``, `` and `useProductSearch`.** Pass the attribute names a card renders — e.g. `:product-track-attributes="['MPN']"` — and they arrive on `product.attributes` for every item in the result, ready to read from a card slot. `useProductInfo` has had an option of this name since the PDP work; the grid side simply never forwarded one, so hosts that set it in their portal config saw it silently ignored on listings and had to fetch attributes themselves in a second request. Requires `propeller-sdk-v2` >= 0.16.0, where the `category` and `products` operations gained `$attributeResultSearchInput` and `ProductGridFields` gained the matching `attributes(input:)` selection. Naming the attributes you render is not just a payload optimisation — it is the correct behaviour. With no input the server returns the *first page* of a product's attributes (12 per product), so on a product carrying more than 12 the ones on later pages are missing with no error. Filtering to the names you need also cut a 24-product category response from ~168 KB to ~124 KB in our testing. Matches the same addition in `propeller-v2-react-ui` 0.12.0. ## [0.9.4] - 2026-07-31 ### Fixed - **The add-to-cart button overflowed its product card in narrow columns.** The submit button is `flex-1`, but a flex item defaults to `min-width: auto` and so refuses to shrink below its content width — icon plus label plus `px-6` of padding. In a slider or a dense grid the button ran past the card's edge instead of fitting inside it. Longer non-English labels hit this first: Dutch "Toevoegen" is roughly twice the width of the "Add" the padding was sized around. The button now carries `min-w-0`, eases its padding to `px-3 sm:px-6`, and wraps its label in a `truncate` span, so it shrinks to the column and ellipsises rather than overflowing. Same fix for ``'s "View cluster" link, which had the identical shape. - **Hovering a card's CTA lit up the whole card.** The card root is a `group` with `hover:shadow-md`, so hovering the button — a descendant — raised the card shadow, shifted its border and zoomed the product image at the same time as the button's own hover state. Three things answering one intent read as the card being clickable rather than the button. While the pointer is on a CTA the card-level highlight and the image zoom now stand down and the button owns the hover; moving anywhere else on the card is unchanged. Browsers without `:has()` keep the previous behaviour. ## [0.9.3] - 2026-07-31 ### Fixed - **`` hid add-to-cart from signed-in users in a semi-closed portal.** It gated the control on `portalMode === 'open'`, so the whole mode lost it rather than just anonymous visitors — the same defect `ProductGrid` had before 0.6.0. Sliders now gate on the shared `isContentHidden(portalMode, user)` like the grid, so a signed-in shopper keeps add-to-cart on cross-sells, up-sells and CMS product blocks. ### Added - **`allowAddToCart` on ``** — lets a host hide the control the way `ProductGrid` already allows. Defaults to `true`; a semi-closed portal still withholds it from anonymous visitors regardless. ## [0.9.2] - 2026-07-31 ### Fixed - **`` and `` dropped `onLoginClick`, so the log-in action did nothing.** In a semi-closed portal `ProductCard` replaces add-to-cart with `` and calls `onLoginClick` — but both listing components forward card props explicitly, and neither passed it. The callback was therefore unreachable from any listing: anonymous visitors got a button that looked clickable and went nowhere. Missed when the semi-closed gating landed in 0.6.0. Both now forward it alongside the other card callbacks. ## [0.9.1] - 2026-07-30 ### Fixed - **`menuStyle="accordion"` rendered nothing above `md`.** The accordion is the mobile drawer for every style, so its `