@decocms/apps-magento 7.64.2 → 7.65.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@decocms/apps-magento",
-  "version": "7.64.2",
+  "version": "7.65.0",
   "type": "module",
   "description": "Deco commerce app: Magento integration",
   "repository": {
@@ -26,9 +26,9 @@
     "lint:unused": "knip"
   },
   "dependencies": {
-    "@decocms/blocks": "7.64.2",
-    "@decocms/apps-commerce": "7.64.2",
-    "@decocms/tanstack": "7.64.2"
+    "@decocms/blocks": "7.65.0",
+    "@decocms/apps-commerce": "7.65.0",
+    "@decocms/tanstack": "7.65.0"
   },
   "peerDependencies": {
     "react": "^19.0.0",

package/src/README.md

@@ -13,7 +13,7 @@ the original deco-cx/apps repo and need adaptation passes (Deno → Node,
 ctx-based to client-based state access, cookie helpers from
 `@decocms/start/sdk/cookie`).
 
-A real-world consumer (deco-sites/granadobr-tanstack) is wiring magento
+A real-world consumer (a production Magento storefront) is wiring magento
 in-site today using a thin adapter that wraps the legacy `magento/mod.ts`
 shape. Their adapter is the migration target — once this package covers
 the surface area they need, the in-site copy goes away.
@@ -54,7 +54,7 @@ above is a hard requirement of this port.
 
 ## Why a stub now
 
-The deco-sites/granadobr-tanstack migration hit a HIGH parity finding:
+A production Magento storefront's migration hit a HIGH parity finding:
 
 ```
 invoke(magento/loaders/features) failed: handler not found

package/src/__tests__/graphql.test.ts

@@ -148,15 +148,15 @@ describe("transformFilterGraphQL — merge order", () => {
 
 describe("formatUrlSuffix", () => {
 	it("strips a single leading slash", () => {
-		expect(formatUrlSuffix("/granado/")).toBe("granado/");
+		expect(formatUrlSuffix("/acme/")).toBe("acme/");
 	});
 
 	it("appends trailing slash when missing", () => {
-		expect(formatUrlSuffix("granado")).toBe("granado/");
+		expect(formatUrlSuffix("acme")).toBe("acme/");
 	});
 
 	it("leaves trailing slash alone", () => {
-		expect(formatUrlSuffix("granado/")).toBe("granado/");
+		expect(formatUrlSuffix("acme/")).toBe("acme/");
 	});
 });
 

package/src/client.ts

@@ -58,7 +58,7 @@ export interface MagentoCartConfigs {
 }
 
 export interface MagentoConfig {
-	/** Magento storefront base URL, e.g. `https://loja.granado.com.br/` */
+	/** Magento storefront base URL, e.g. `https://loja.acme.com.br/` */
 	baseUrl: string;
 	/** Bearer token for `Authorization` header on admin REST calls */
 	apiKey: string;

package/src/middleware.ts

@@ -5,8 +5,8 @@
  * after checkout (`changeCardIdAfterCheckout`) and seeded the
  * `form_key` for anonymous sessions. Both flows touched response
  * headers and `customer/section/load` endpoints — non-trivial port,
- * deferred to a follow-up PR. Today the consumer site (granadobr-
- * tanstack) handles cart reconciliation on the client.
+ * deferred to a follow-up PR. Today a production Magento storefront
+ * handles cart reconciliation on the client.
  *
  * Shape matches `@decocms/apps-commerce/app-types` so it can be
  * plugged into the autoconfig pipeline once magento is registered

package/src/utils/client/types.ts

@@ -24,7 +24,7 @@ export interface Customer {
 }
 
 /**
- * `carbono-customer` slice. Granado-specific overlay that mirrors the
+ * `carbono-customer` slice. A storefront-specific overlay that mirrors the
  * `customer` slice plus a website/store id pair and a normalized email.
  * Other magento sites that don't run the Carbono module will get this
  * absent; loaders/user.ts checks for it before mapping to a Person.

package/src/utils/transform.ts

@@ -6,8 +6,8 @@
  * Subset of `deco-cx/apps/magento/utils/transform.ts` — only the
  * functions the PDP loader needs (toProduct, toOffer, toImages, toURL,
  * toBreadcrumbList, toSeo). The GraphQL-side helpers (toProductGraphQL,
- * toAggOfferGraphQL, toProductListingPageGraphQL, …) and the Granado-
- * specific helpers (toReviewAmasty, toLiveloPoints) are intentionally
+ * toAggOfferGraphQL, toProductListingPageGraphQL, …) and the
+ * storefront-specific helpers (toReviewAmasty, toLiveloPoints) are intentionally
  * excluded — they land in separate follow-up PRs alongside the loaders
  * that consume them.
  *