@multiplatform.one/cli 7.7.6 → 7.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@multiplatform.one/cli",
-  "version": "7.7.6",
+  "version": "7.10.0",
   "description": "multiplatform.one cli — mpo init / create-multiplatform-app",
   "keywords": [
     "create-multiplatform-app",
@@ -61,7 +61,7 @@
     "nano-spawn": "^2.1.0",
     "yaml": "^2.8.3",
     "yocto-spinner": "^1.1.0",
-    "@multiplatform.one/utils": "7.7.6"
+    "@multiplatform.one/utils": "7.10.0"
   },
   "devDependencies": {
     "@types/inquirer": "^9.0.9",

package/src/commands/initApp.spec.ts

@@ -429,6 +429,10 @@ describe("initApp generator", () => {
         const readme = readFileSync(join(root, "README.md"), "utf-8");
         expect(readme).toContain("## Frappe backend");
         expect(readme).toContain("## Keycloak auth");
+        // Fixtures are a supported way to run the generated app (MPO-228),
+        // so the README has to say how.
+        expect(readme).toContain("### Running against fixtures, with no bench");
+        expect(readme).toContain("frappe: { fixtures }");
       });
 
       // Two measured first-boot failures, both cheap to reintroduce. The

package/templates/pieces/frappe/universal/README.md.partial

@@ -30,3 +30,60 @@ bench start
 Then set `FRAPPE_URL=http://__NAME__.localhost:8000` (or keep
 `http://localhost:8000` and make the site the default with
 `bench use __NAME__.localhost`) and restart `pnpm dev`.
+
+### Running against fixtures, with no bench
+
+`createApp` takes a fixture corpus, so the app runs with no server and no
+network. Hand `frappe.fixtures` a `FixtureProvider` in
+`apps/__NAME__/src/app.ts`:
+
+```ts
+import { createApp } from "@multiplatform.one/core";
+import { InMemoryFixtureProvider } from "@multiplatform.one/frappe";
+import { themeConfig } from "@package/themes";
+
+const fixtures = new InMemoryFixtureProvider({
+  Customer: [
+    { name: "CUST-0001", doctype: "Customer", customer_name: "Acme" },
+    { name: "CUST-0002", doctype: "Customer", customer_name: "Globex" },
+  ],
+});
+
+export const { AppProvider, useAppConfig, withApp } = createApp({
+  theme: themeConfig,
+  frappe: { fixtures },
+});
+```
+
+`FrappeTable`, `FrappeList` and the other collection-backed components then
+read from the corpus. Writes land in it too, so create/update/delete work for
+the session.
+
+Two things follow from setting `fixtures`:
+
+- the provider mounts without `FRAPPE_ENABLED=1`, and
+- `baseURL` takes no fallback. Only a `baseURL` you pass explicitly is used,
+  so `BASE_URL` cannot quietly point fixture reads at the app's own origin.
+
+Column labels and filter fields come from DocType metadata, which lives in
+the corpus under the `DocType` doctype (the `getdoctype` shape) when you want
+it:
+
+```ts
+const fixtures = new InMemoryFixtureProvider({
+  DocType: [
+    {
+      name: "Customer",
+      doctype: "DocType",
+      fields: [{ fieldname: "customer_name", fieldtype: "Data", label: "Customer Name" }],
+    },
+  ],
+  Customer: [{ name: "CUST-0001", doctype: "Customer", customer_name: "Acme" }],
+});
+```
+
+Leave it out and the table still renders its rows; it just has no
+metadata-derived filter fields.
+
+To point the same app at a real bench again, drop `fixtures` and set
+`FRAPPE_ENABLED=1` + `FRAPPE_URL` in `.env`.