waygraph 0.15.51 → 0.15.53

package/templates/scaffold/src/flows/mail-verify.flow.ts

@@ -1,85 +0,0 @@
-import { Engine, start, end, withTitle, withHighlightFixtures } from "waygraph";
-import { NavMailpitInboxBlock } from "../map/(external)/mailpit/_nav.block.js";
-import { AssertEmailReceivedBlock } from "../map/(external)/mailpit/_methods/assert-email-received.method.block.js";
-import { OpenMessageBlock } from "../map/(external)/mailpit/_methods/open-message.method.block.js";
-import { AssertEmailContentBlock } from "../map/(external)/mailpit/_methods/assert-email-content.method.block.js";
-import { ExtractEmailLinkBlock } from "../map/(external)/mailpit/_methods/extract-email-link.method.block.js";
-import { NavVerificationLinkBlock } from "../map/(app_base)/home/nav-verification-link.block.js";
-import "../map/(external)/mailpit/_page.block.js";
-import { MailpitSel } from "../map/(external)/mailpit/_sel.js";
-
-const engine = new Engine();
-
-/**
- * Cross-origin mail demo, QA-rich: navigate to a real Mailpit inbox (a real,
- * separate web UI - not this app), confirm the email actually arrived,
- * open it, confirm its body says what it's supposed to, read a link
- * straight out of the DOM, then navigate back into the app with it - six
- * atomic Blocks, no mail-catcher REST API anywhere.
- *
- * The four mail-reading Blocks (`assert-email-received`, `open-message`,
- * `assert-email-content`, `extract-email-link`) are reusable across any
- * number of different email scenarios in a project (signup confirmation,
- * password reset, magic link, ...) with zero new Blocks per scenario - only
- * mem varies per run: `ExpectedRecipient` (who), `ExpectedLinkPattern`
- * (which link in the body to follow), `ExpectedEmailContent` (what the body
- * should say). This particular flow wires them to this scaffold's own
- * "verified" landing route (`nav-verification-link`, app-specific by
- * nature - a different scenario would use a different landing Nav) - see
- * tests/mail-verify.spec.ts for two different scenarios driven through the
- * same four mail-reading Blocks.
- *
- * Needs a real Mailpit instance reachable at WAYGRAPH_MAIL_URL (default
- * http://127.0.0.1:8025) with a message already waiting for
- * ExpectedRecipient's email - see tests/mail-verify.spec.ts for how the test
- * drives this end to end (spins up a real Mailpit container, sends a real
- * email, then runs this exact flow) - including the negative cases: no email
- * arriving, or content that doesn't match, each fail loud, naming
- * themselves, not a silent pass.
- */
-export const mailVerifyFlow = withHighlightFixtures(
-  withTitle(
-    engine.defineFlow([
-      start,
-      NavMailpitInboxBlock,
-      AssertEmailReceivedBlock,
-      OpenMessageBlock,
-      AssertEmailContentBlock,
-      ExtractEmailLinkBlock,
-      NavVerificationLinkBlock,
-      end,
-    ]),
-    "Scaffold: Cross-origin mail verification (QA-rich)",
-  ),
-  {
-    "assert-email-received": {
-      stubAfter: {
-        note: {
-          selector: MailpitSel.messageRow,
-          label: "AC · email arrived",
-          detail: "Confirmed before opening anything.",
-          tag: "AC",
-        },
-      },
-    },
-    "assert-email-content": {
-      stubAfter: {
-        note: {
-          selector: MailpitSel.previewIframe,
-          label: "AC · email body matches expected copy",
-          tag: "AC",
-        },
-      },
-    },
-    "extract-email-link": {
-      stubAfter: {
-        note: {
-          selector: MailpitSel.previewIframe,
-          label: "AC · link found",
-          detail: "Read from the message preview iframe.",
-          tag: "AC",
-        },
-      },
-    },
-  },
-);

package/templates/scaffold/src/flows/shop.flow.ts

@@ -1,74 +0,0 @@
-import {
-  Engine,
-  start,
-  end,
-  withTitle,
-  withHighlightFixtures,
-  withSessionReset,
-  withMemStub,
-  registerMemStub,
-} from "waygraph";
-import { NavHomeBlock } from "../map/(app_base)/home/_nav.block.js";
-import { AddItemBlock } from "../map/(app_base)/home/_methods/add-item.effect.block.js";
-import { AssertItemAddedBlock } from "../map/(app_base)/home/_methods/assert-item-added.method.block.js";
-import { RemoveItemBlock } from "../map/(app_base)/home/_methods/remove-item.effect.block.js";
-import { ClearCartBlock } from "../map/(app_base)/home/_methods/clear-cart.method.block.js";
-import { SelectedItem } from "../states/demo.mem-keys.js";
-import "../map/(app_base)/home/_page.block.js";
-
-const engine = new Engine();
-
-/**
- * memStub: a real fixture row (`alpha`/`Alpha`), registered once so this Flow never needs
- * --data at all. Still override-able - `--data '{"demo.selectedItem":{"id":"beta",...}}'`
- * wins over this registration, same as any other memStub (see docs/REFERENCE.md's own
- * "memStub - fake values for requires" section).
- */
-registerMemStub(SelectedItem.key, () => ({ id: "alpha", name: "Alpha" }));
-
-/**
- * Effect + Method demo. `requires: [SelectedItem.key]` (on `add-item`) is filled automatically
- * by the memStub registration above - no --data needed. Override it with real data, or use
- * `waygraph auto` which fills SelectedItem via instanceOptions instead:
- *
- *   waygraph demo --blocks shopFlow                                    # memStub fills it
- *   waygraph demo --blocks shopFlow --data '{"demo.selectedItem":{"id":"beta","name":"Beta"}}'
- *   waygraph auto   # after landing on home, pick Add Alpha / Add Beta / Remove ...
- *
- * Add -> assert it actually landed (mem-matched Remove button + cart count,
- * only provable from the method's real effect, not a static page state) ->
- * Remove that same row (per-item Effect, `remove-item`) -> Add again ->
- * Clear cart (bulk Method, `clear-cart`) - keeps both the per-item and bulk
- * clear paths atomic and each wired into a real flow, not orphaned.
- */
-export const shopFlow = withMemStub(
-  withHighlightFixtures(
-    withTitle(
-      withSessionReset(
-        engine.defineFlow([
-          start,
-          NavHomeBlock,
-          AddItemBlock,
-          AssertItemAddedBlock,
-          RemoveItemBlock,
-          AddItemBlock,
-          ClearCartBlock,
-          end,
-        ]),
-      ),
-      "Scaffold: Shop (Effect + clear)",
-    ),
-    {
-      "add-item": {
-        stubAfter: {
-          cart: {
-            label: "AC · item in cart",
-            detail: "Cart count bumped after Add.",
-            tag: "AC",
-            duration: true,
-          },
-        },
-      },
-    },
-  ),
-);