@zalify/storefront-kit 0.5.0 → 0.5.1

package/dist/editor/bootstrap.d.ts

@@ -10,8 +10,10 @@ export interface EditorDocuments {
 export declare const TEMPLATE_TYPES: readonly ["index", "product", "collection", "list-collections", "page", "blog", "article", "cart", "search", "404", "password", "gift_card"];
 /**
  * What is wrong with a set of template names, for a storefront's own tests:
- * names must be `<type>` or `<type>.<suffix>`, and a type that has alternates
- * must also have its default. Empty means the editor can lay them out.
+ * names must be `<type>` or `<type>.<suffix>` with a known type. A default is
+ * not required next to alternates — a site with `page.about` but no generic
+ * page route must not invent one; the editor groups such alternates itself.
+ * Empty means the editor can lay them out.
  */
 export declare function templateNameProblems(names: readonly string[]): string[];
 /** Only list routes the app can actually render; never fabricate handles. */

package/dist/editor/bootstrap.js

@@ -15,13 +15,13 @@ export const TEMPLATE_TYPES = [
 ];
 /**
  * What is wrong with a set of template names, for a storefront's own tests:
- * names must be `<type>` or `<type>.<suffix>`, and a type that has alternates
- * must also have its default. Empty means the editor can lay them out.
+ * names must be `<type>` or `<type>.<suffix>` with a known type. A default is
+ * not required next to alternates — a site with `page.about` but no generic
+ * page route must not invent one; the editor groups such alternates itself.
+ * Empty means the editor can lay them out.
  */
 export function templateNameProblems(names) {
     const problems = [];
-    const known = new Set(names);
-    const needsDefault = new Set();
     for (const name of names) {
         if (name.startsWith('customers/'))
             continue;
@@ -29,12 +29,6 @@ export function templateNameProblems(names) {
         if (!TEMPLATE_TYPES.includes(type)) {
             problems.push(`"${name}": unknown template type "${type}" — use <type>.<suffix>, e.g. "page.${name.replace(/[^a-z0-9]+/gi, '-').toLowerCase()}"`);
         }
-        else if (name !== type && !known.has(type)) {
-            needsDefault.add(type);
-        }
-    }
-    for (const type of needsDefault) {
-        problems.push(`"${type}.*" alternates exist but the default "${type}" template is not registered`);
     }
     return problems;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zalify/storefront-kit",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "type": "module",
   "description": "The Zalify storefront SDK: framework-agnostic commerce logic (/commerce), the theme contract types and validators (/schemas), the canvas-editor bridge (/editor), and the React theme engine + shared components (/ui, /react/server). Consumed as TypeScript source inside the zalify-storefronts monorepo; published as compiled ESM + d.ts.",
   "license": "SEE LICENSE IN LICENSE.md",

package/skills/zalify-storefront-editor/SKILL.md

@@ -52,8 +52,9 @@ and from the editor.
   `page.<suffix>`.
 - Assert `templateNameProblems(names)` (from
   `@zalify/storefront-kit/editor/bootstrap`) is empty in the repo's tests.
-- A type that has alternates also registers its default (`page` next to
-  `page.about`). The editor nests alternates under the default.
+- Register a type's default (`page`) only when the app has a route that renders
+  it. Alternates without a default are fine: the editor groups them under the
+  type. Never add a template just to satisfy the picker.
 - `writePath` is `<templates dir>/<name>.json`; the file on disk has the same
   name. Renaming a template renames the file and every route that loads it.
 - Only advertise a preview route the app can really render. Resource routes

package/src/editor/bootstrap.ts

@@ -26,13 +26,13 @@ export const TEMPLATE_TYPES = [
 
 /**
  * What is wrong with a set of template names, for a storefront's own tests:
- * names must be `<type>` or `<type>.<suffix>`, and a type that has alternates
- * must also have its default. Empty means the editor can lay them out.
+ * names must be `<type>` or `<type>.<suffix>` with a known type. A default is
+ * not required next to alternates — a site with `page.about` but no generic
+ * page route must not invent one; the editor groups such alternates itself.
+ * Empty means the editor can lay them out.
  */
 export function templateNameProblems(names: readonly string[]): string[] {
   const problems: string[] = [];
-  const known = new Set(names);
-  const needsDefault = new Set<string>();
   for (const name of names) {
     if (name.startsWith('customers/')) continue;
     const type = name.split('.')[0];
@@ -40,13 +40,8 @@ export function templateNameProblems(names: readonly string[]): string[] {
       problems.push(
         `"${name}": unknown template type "${type}" — use <type>.<suffix>, e.g. "page.${name.replace(/[^a-z0-9]+/gi, '-').toLowerCase()}"`,
       );
-    } else if (name !== type && !known.has(type)) {
-      needsDefault.add(type);
     }
   }
-  for (const type of needsDefault) {
-    problems.push(`"${type}.*" alternates exist but the default "${type}" template is not registered`);
-  }
   return problems;
 }