@propeller-commerce/propeller-v2-react-ui 0.27.0 → 0.29.0

package/CHANGELOG.md

@@ -8,6 +8,125 @@ 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.29.0] - 2026-10-05
+
+### Fixed
+
+- **Listings no longer drop the company's orderlist on a client-side fetch.**
+  `useProductSearch` sent `applyOrderlists: false` whenever the caller passed
+  no explicit `orderlistIds` — which is every app — so the backend was told to
+  ignore the company's own orderlists. The server render omits the flag and is
+  correctly scoped, so a category page painted the right products and then the
+  first sort, filter, page or company change replaced them with the unscoped
+  catalogue, priced and orderable. The flag is now sent only when the caller
+  actually asks for it, in both the grid fetch and the search-bar preview.
+  `useQuickOrder` had the same default, which let a bulk paste resolve SKUs
+  outside the contract.
+
+  Callers that relied on the implicit `false` for an intentionally unscoped
+  listing must now pass `applyOrderlists={false}` explicitly.
+
+- **`<ProductSlider>` is scoped to the viewer and priced for their company.**
+  `fetchProducts` sent no `userId`, no `companyId` and no
+  `priceCalculateProductInput`, and resolved its ids through the flat
+  `products` resolver, which does not apply orderlist scoping. A featured
+  slider therefore showed products outside the company's assortment at the
+  default company's prices. Its `filterToAssortment` step — whose only job is
+  dropping out-of-assortment crossupsells — asked the same resolver and so
+  could never filter anything. Both now go through `category.products` over
+  `configuration.baseCategoryId`, the path the grid and quick order already
+  use. Without a resolved base category the primary fetch returns nothing
+  rather than an unscoped list, while the crossupsell check falls through to
+  the unverified items so a slider is never blanked by a failed check.
+
+- **Cart quantity steppers keep the line on the order grid.** `CartItem` read
+  `minimumQuantity` and the step but used them only to disable the decrement
+  button: the buttons added or subtracted the step from whatever was there, so
+  a line already off the grid stayed off it (min 2, step 3: 9 → 12). The typed
+  field committed only values at or above the minimum, so clearing it or typing
+  below the minimum left the old quantity stuck. Both steppers now resolve to
+  the grid first, and editing goes through a draft value that resolves on blur
+  — the same rule `<AddToCart>` and `<QuickOrder>` already followed.
+
+- **Add to cart recovers when the remembered cart is gone.** A cart ordered in
+  another browser or deleted leaves its id behind in the host's storage, and
+  every later `cartAddItem` answered `CART_NOT_FOUND_ERROR`. Nothing forgot the
+  id, so each retry failed identically and the badge kept showing the dead
+  cart. `addItem` now forgets it and starts a fresh cart once, then re-adds;
+  the recovery is bounded because cart initialisation only ever returns an
+  `OPEN` cart, and it is skipped when the caller passed `createCart: false`.
+
+- **`useProductInfo` no longer sends every company orderlist as an allowlist.**
+  It fetched all orderlists for the company and passed their ids to
+  `product(orderlistIds:)` with no filter on type, so a NEGATIVE (exclusion)
+  list was applied as an allowlist and inverted the filter. Scoping is left to
+  the backend, which merges positive and negative lists itself — one fewer
+  request per product page.
+
+### Changed
+
+- **The min/step rule comes from `propeller-v2-core-ui`.** `AddToCart`,
+  `QuickOrder` and `CartItem` each carried their own copy, and they had
+  drifted — two of them divided by an unguarded step. All now call
+  `resolveOrderableQuantity` from core-ui 0.11.0, which is the new minimum for
+  this package.
+
+## [0.28.0] - 2026-10-02
+
+### Added
+
+- **`imgComponent` on `<PropellerDepsProvider>` — one setting routes every
+  image through the host’s image component.** Components rendered a bare
+  `<img src="https://media.…">`, so catalog images were fetched straight from
+  the media CDN. That CDN sends no `X-Robots-Tag` and serves no `robots.txt`,
+  so those images sat outside the storefront’s crawler directives and got none
+  of the host framework’s image optimisation. The existing `imageComponent`
+  slot could not close this: it takes a `product`/`cluster` and resolves the
+  URL itself, so it only fitted five surfaces, and the other nineteen image
+  sites had already resolved a URL string by render time. Set `imgComponent`
+  once on the provider and images across the package route through it,
+  including components added later. Optional — omitting it keeps the previous
+  markup. (PWP-1001)
+- **`<PropellerImg>` and `useImgComponent()` are exported.** Hosts composing
+  their own cards get the same seam; `<PropellerImg>` is also on the `/pure`
+  entry for Server Components.
+- **`OrderItemCard` accepts `imgComponent` as a prop.** It is `@rsc-safe` and
+  reads no context, so the provider cannot reach it — same direct-prop
+  convention as its existing `priceComponent` / `stockComponent`.
+
+### Changed
+
+- **Nineteen image sites now render `<PropellerImg>`** across `ProductCard`,
+  `ClusterCard`, `ProductGallery`, `CartItem`, `OrderItemCard`, `SearchBar`,
+  `ProductBundles`, `MachineCard`, `AddToCart`, `QuickOrder`, `ItemsOverview`,
+  `FavoriteListItem`, `FavoriteListDetails`, `ClusterOptions`,
+  `ClusterConfigurator`, `CartBonusItems` and `DefaultProductImage`. Markup is
+  unchanged when no component is injected.
+- **Carrier and payment-provider logos stay plain `<img>`.** Their domains sit
+  outside the host’s image allowlist, so routing them through a framework
+  image component would stop them loading. They are catalog-external and not
+  crawlable.
+- **`npm run check:img` fails the build on a raw `<img>`.** The seam only holds
+  if new components use it, and a raw `<img>` opts a surface out silently.
+  Wired into `validate` and `prepublishOnly`.
+
+### Fixed
+
+- **The "no image" placeholder was two different icons.** Cards, favourites and
+  `DefaultProductImage` drew one glyph; cart rows, the cart drawer, bundles, the
+  add-to-cart modal and the checkout overview drew another, at a heavier stroke
+  weight — so the same missing-image product looked like two different states
+  depending on which surface showed it. All of them now use the card icon at a
+  consistent stroke weight. The machine card keeps its own glyph, which is
+  deliberate.
+- **The cart drawer’s image box did not centre its contents.** It overrides
+  `CartItem.Image`’s class, and the override dropped the flex centring, so the
+  placeholder sat top-left at its natural size instead of filling the box.
+- **Placeholder icons were exposed to screen readers.** They carry no
+  information the row does not already state in text, so they now set
+  `aria-hidden`, matching what `DefaultProductImage` already did.
+---
+
 ## [0.27.0] - 2026-09-28
 
 ### Fixed