@propeller-commerce/propeller-v2-react-ui 0.16.0 → 0.19.0

package/CHANGELOG.md

@@ -8,18 +8,152 @@ 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.19.0] - 2026-08-26
+
+### 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 and hit the bug below.
+- **`currency` on `ProductCardProps` / `ProductGridProps`**, resolved from
+  `<PropellerProvider>` like `ClusterCard` already did.
+- **`className` on `CartSummaryProps`** and **`inputClassName` on
+  `SearchBarProps`**, merged over the defaults through `tailwind-merge`.
+- **`configuration` on `OrderItemCardProps`** — supply the host's URL builders
+  and the item link is generated the way every other link on the storefront is.
+- **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.
+
+### Fixed
+
+- **`addItem` could not add more than one product per tick.** It resolved the
+  cart id from React state, which does not update until the next render, so a
+  loop sent the same stale id every iteration: the 2nd..nth add failed with
+  "No cart ID provided", or — with `createCart` — quietly started a NEW cart per
+  product so only the last one survived. Neither failure throws, so both looked
+  like the adds had simply vanished. The id now lives in a ref written the
+  moment a cart resolves.
+- **Cart lines lost their images unless every add path passed `configuration`.**
+  The media arguments are optional and nothing warned; the mutation succeeded
+  and the returned items carried no `imageVariants` at all, so the shopper saw
+  empty tiles for products with perfectly good PIM images — two screens away
+  from the call site. The hook now defaults them; an explicit `configuration`
+  still wins.
+- **A non-euro shop could not change the currency in the catalogue.**
+  `ProductGrid` resolved a currency and never forwarded it, so every card fell
+  through to the package's `€`. `GridFilters`' price inputs and the active
+  price-filter chip hardcoded the glyph too — the chip had no prop and no class,
+  so no userland fix existed.
+- **Prices used Dutch separators in every language.** Number format now follows
+  the storefront language via core-ui's `localeForLanguage`, so an English shop
+  renders `£3.45` rather than `£ 3,45`. Components that format money take a
+  `language` prop, resolved from the provider where they already read infra.
+- **Search autosuggest and order-item links dropped the locale prefix.** Both
+  built `/product/:id/:slug` from literals instead of the host's URL builders,
+  so on a prefixed storefront they sent the visitor to the default language.
+  They now use `configuration.urls` when supplied, with the literals as a bare-
+  mount fallback.
+- **`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.
+- **`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.
+- **`ProductBundles`' add button read "In cart"**, a status rather than the
+  action it performs, where every other cart control in the package says
+  "Add to cart".
+- **`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
+
+- `AddToCartProps.onAddToCart` may return a promise, and `useCart` awaits the
+  override. Matches the widened slot contract in core-ui 0.7.0.
+- Requires `@propeller-commerce/propeller-v2-core-ui` `^0.7.0`.
+
+## [0.18.0] - 2026-08-20
+
+### 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.
+  - `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 `<a>`, so
+    a buyer fetching the spreadsheet left no trace. Navigation is untouched.
+
+### Notes
+
+- `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.17.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, while the
+  same override on `CartIconAndSidebar` appeared to work only because its
+  default happened to lose anyway. Every override site now merges through
+  `tailwind-merge`, so a conflicting utility is replaced rather than raced.
+  59 sites across 47 components; BEM hooks and non-conflicting utilities are
+  untouched.
+
+- **Anonymous catalog listings were scoped differently on the client than on
+  the server.** Listing hooks 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
+  therefore asked different questions, and 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 five
+  listing hooks (`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 can scope to
+  it. Same route `baseCategoryId` takes; no module guesses it.
+
 ## [0.16.0] - 2026-08-12
 
 ### Fixed
 
-- **Localized names and slugs ignored the storefront language (PWP-936 /
-  PWP-940).** A localized array carries one entry per authored language in
+- **Localized names and slugs ignored the storefront language.** A localized array carries one entry per authored language in
   catalog order, so `names[0]` / `slugs[0]` is the catalog's DEFAULT language,
   not the storefront's. Thirteen sites read index 0 unconditionally while
   eleven others resolved by language correctly. Now all of them go through
   `getLocalizedValue`, which prefers the active language and falls back to any
   translation that has a value:
-  - `ClusterOptions` — option group and option product names (PWP-936)
+  - `ClusterOptions` — option group and option product names
   - `FavoriteListItem`, `FavoriteListDetails` — product and cluster names
   - `ItemsOverview` — item, bundle-leader, bundle-item and child-option names
   - `ProductBundles` — bundle item names
@@ -29,8 +163,7 @@ between minor versions; breaking changes are called out below and in
 
   The three slug sites are the ones that actually broke: they emitted
   default-language URLs on every non-default locale.
-- **`useCart` never adopted a cart id that arrived after mount (PWP-938 /
-  PWP-937).** The id was seeded once with `useState(options.cartId || '')` and
+- **`useCart` never adopted a cart id that arrived after mount.** The id was seeded once with `useState(options.cartId || '')` and
   only reassigned from the hook's own cart-creation path, so a component that
   mounted before the cart resolved held `''` permanently. `CartIconAndSidebar`
   renders in the header on the first paint of every page, so its "Request
@@ -50,7 +183,7 @@ between minor versions; breaking changes are called out below and in
   `useInfraProps`, like the other catalog components. Passing it explicitly
   still wins.
 - The favorites list's add-product button default now reads "Add product to
-  favorite list" instead of "Add product directly to this wishlist" (PWP-939).
+  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".
 
@@ -58,7 +191,7 @@ between minor versions; breaking changes are called out below and in
 
 ### Fixed
 
-- **Checkout step 3 opened with nothing selected on a fresh cart (PWP-934).**
+- **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
@@ -97,7 +230,7 @@ between minor versions; breaking changes are called out below and in
 ### Fixed
 
 - **The product specifications table emptied out in a language the catalogue is
-  only partly translated into** (PWP-928). A localized list carries only the
+  only partly translated into**. A localized list carries only the
   languages someone authored, so asking for one nobody wrote returns nothing —
   it does not fall back. `ProductSpecifications` matched strictly on
   `language === props.language`, which failed twice over: the label fell through
@@ -203,7 +336,7 @@ between minor versions; breaking changes are called out below and in
   fall back to, and 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 happened to be
-  translated (PWP-927).
+  translated.
 
   `names` and `slugs` are now fetched unfiltered — every translation — and
   `mapCategory` picks the active language, falling back to whichever translation

package/README.md

@@ -307,9 +307,17 @@ and pass it once.
 | `language`      | `string`                      | Locale code used to resolve localized content (e.g. `'NL'`, `'EN'`).        |
 | `includeTax`    | `boolean`                     | Whether displayed prices include tax.                                       |
 | `currency`      | `string`                      | Currency symbol for price formatting. Default: `'€'`.                       |
-| `configuration` | `unknown`                     | Free-form config bag forwarded to components — stuff your own settings in.  |
+| `configuration` | `unknown`                     | Config bag forwarded to components. Recognized keys: `baseCategoryId`, `anonymousUserId` (see below), image filters — plus anything of your own. |
 | `portalMode`    | `string`                      | Storefront mode (e.g. `'open'`, `'closed'`).                                |
 
+**`configuration.anonymousUserId`** — the channel's guest account. Listing
+hooks scope logged-out catalog queries to it, so the client asks the same
+question your server-rendered seed did. Resolve it server-side (only the
+server can reach the channel) and pass it in; when it's absent, anonymous
+queries send no `userId` and the backend falls back to the api key's own
+scope. Getting this wrong is invisible — the grid renders, just with the
+wrong assortment.
+
 The `value` object is reactive — when your auth/company/language state
 changes, recompute it (memoize on those dependencies) and the provider
 propagates the new value. Components re-render with fresh infra; service
@@ -584,15 +592,19 @@ cascade order — no `!important` needed:
 .propeller-breadcrumbs__separator { display: none; }
 ```
 
-**3. Per-instance `className`** — every component appends `props.className`
-on its root, so a one-off override is a regular prop:
+**3. Per-instance `className`** — every component merges `props.className`
+into its root classes, so a one-off override is a regular prop:
 
 ```tsx
 <ProductCard product={p} className="ring-2 ring-yellow-400" />
 ```
 
-`className` **adds to** the base classes — it doesn't replace them. To strip
-a default, use a BEM hook.
+The merge runs through [`tailwind-merge`](https://github.com/dcastil/tailwind-merge)
+(since 0.17.0), so an override **replaces** the base utility it conflicts with
+rather than racing it in the cascade — `iconClassName="text-cocoa"` on a
+component whose default is `text-white` now renders cocoa. Non-conflicting
+utilities and the BEM hooks are left untouched. To remove a default outright
+(rather than override it), use a BEM hook.
 
 See [STYLING.md](./STYLING.md) for the full token list, the complete BEM
 hook catalog, and the cascade rationale.