@propeller-commerce/propeller-v2-react-ui 0.15.11 → 0.18.0

package/CHANGELOG.md

@@ -8,6 +8,113 @@ 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.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
+  (PWP-942 #17).** 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 (PWP-942 #22).** 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 since PWP-913; 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
+  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)
+  - `FavoriteListItem`, `FavoriteListDetails` — product and cluster names
+  - `ItemsOverview` — item, bundle-leader, bundle-item and child-option names
+  - `ProductBundles` — bundle item names
+  - `OrderItemCard` — item name, child-item names, and **the cluster/product
+    slugs used to build the item's link**
+  - `SearchBar` — **the slug used to build each autosuggest result's link**
+
+  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
+  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
+  authorization" button rendered enabled, fired, and returned `err('No cart')`
+  with nothing sent — the reported "cannot submit purchase request". The id is
+  now derived from the prop on every render. `processCart` was affected the
+  same way.
+
+### Changed
+
+- **BREAKING (behavioural, hosts should act):** `OrderItemCard` gains a
+  `language` prop. The component is exported from the RSC-safe `/pure` entry
+  and reads no context by design, so a host that renders it directly must pass
+  `language` or it keeps resolving in the catalog's default language.
+  `OrderBonusItems` forwards its own resolved language automatically.
+- `ClusterOptions` resolves `language` from `<PropellerProvider>` via
+  `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).
+  Hosts that translate `FavoriteListDetails.addProductDirectly` should update
+  their own copy — "favorite list" is the agreed term, not "wishlist".
+
 ## [0.15.11] - 2026-08-11
 
 ### Fixed

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.