@usequeek/theme-kit 0.1.21 → 0.1.22

package/utils/menu-link.ts

@@ -17,7 +17,7 @@ export function menuItemToHref(item: MenuItem, basePath: string = ''): string {
       const href = `${basePath}/${item.ref}`;
       const anchor = item.meta?.anchor;
       // href may already end in "/" (the home page's ref is normalized to
-      // "/" — see MenuResource::normalizeHomeRefs) — never emit a doubled
+      // "/") — never emit a doubled
       // slash before the fragment.
       return anchor ? `${href.replace(/\/$/, '')}#${anchor}` : href;
     }

package/utils/product-media.ts

@@ -14,7 +14,7 @@ export interface MediaFrame {
 
 /**
  * Picks the largest tier a PDP hero should ever request. `view` is capped at
- * 1600px (queek_backend config/media.php) which covers every theme's hero box
+ * 1600px, which covers every theme's hero box
  * at DPR2 — the raw `original` is uncapped and unoptimized.
  */
 function heroUrl(variants: ImageVariants | null | undefined): string | null {

package/utils/product-normalizer.ts

@@ -37,8 +37,8 @@ function toBool(value: unknown, fallback = false): boolean {
 
 /**
  * Same base/sale/compare-at shape as normalizePricing(), but a variant's own price lives on
- * FLAT fields (price/discount_price/compare_at_price/discount_amount — see
- * ProductResource::resolveShopVariants on the backend), never nested under a `pricing` key.
+ * FLAT fields (price/discount_price/compare_at_price/discount_amount), never nested
+ * under a `pricing` key.
  * Reading `variant.pricing?.sale_amount` (as this used to) is always undefined, so every
  * variant silently fell back to the base product's price — picking Denim vs Taupe never
  * changed what was shown, even though the backend had already computed the right number.

package/utils/vendor-host.ts

@@ -1,14 +1,11 @@
 /**
  * Vendor resolution from a hostname: which store is this request for?
  *
- * Lived at `app/middleware.ts` until core needed it — `lib/core/api/products.ts`
- * and `lib/core/sdk/server-store-client.ts` both import from here, which meant
- * core depended on the app. Nothing here is app-specific: it reads env and
- * resolves a slug. (The actual Next middleware is `proxy.ts`; the old filename
- * suggested otherwise and was never that.)
+ * Nothing here is app-specific: it reads env and resolves a slug, so the kit's
+ * server fetchers and a host app's proxy can both import it.
  */
 
-// Mirrors backend config/storefront.php `reserved_slugs`. Keep in sync.
+// Mirrors the API's reserved store slugs. Keep in sync.
 // These are subdomains the storefront proxy must NOT treat as vendor slugs.
 export const RESERVED_VENDOR_SLUGS = new Set([
   // Live platform subdomains
@@ -24,11 +21,10 @@ export const RESERVED_VENDOR_SLUGS = new Set([
   'staff', 'team', 'queek', 'merchant', 'vendor', 'rider', 'customer',
 ]);
 
-// Every sluggable backend model (Vendor, Product, Category, Region, Service —
-// app/Models/*.php `getSlugOptions()`) is Spatie Sluggable output: lowercase
-// alphanumeric, optionally hyphen-separated, never a dot/underscore/uppercase.
-// Anything else cannot be a real slug of any kind, so reject it before any
-// backend round-trip instead of burning calls that all 404. This is what stops
+// Every sluggable API model (Vendor, Product, Category, Region, Service)
+// produces lowercase alphanumeric slugs, optionally hyphen-separated, never a
+// dot/underscore/uppercase. Anything else cannot be a real slug of any kind, so
+// reject it before any API round-trip instead of burning calls that all 404. This is what stops
 // scanners probing `.env`, `.ssh`, `docker-compose.yaml`, `*.php` etc —
 // RESERVED_VENDOR_SLUGS alone only covers known words, not the infinite space
 // of file-extension guesses.