@vendure-platform/create 1.0.1 → 1.0.2-nightly.202610261747.151.1

package/README.md

@@ -174,7 +174,7 @@ See the [Quick Start](https://docs.vendure.io/vendure-platform/getting-started/q
 ## Sharp dependency
 
 Fresh scaffolds declare `sharp` as a server dependency in every edition. The
-pin matches Platform's `@vendure-platform/giftcards` and satisfies Core's
+pin matches Platform's `@vendure-platform/giftcards` and satisfies the Vendure Framework's
 `@vendure/asset-server-plugin` range. This lets Bun and npm share one sharp
 version across both consumers. Without the direct dependency, Bun can choose
 a newer version for the asset server and keep the exact gift cards pin,

package/dist/assets/storefront/package.json

@@ -37,7 +37,7 @@
         "@radix-ui/react-toggle": "^1.1.10",
         "@radix-ui/react-toggle-group": "^1.1.11",
         "@radix-ui/react-tooltip": "^1.2.8",
-        "@vendure-platform/storefront-client": "^1.0.1",
+        "@vendure-platform/storefront-client": "^1.0.2-nightly.202610261747.151.1",
         "class-variance-authority": "^0.7.1",
         "clsx": "^2.1.1",
         "cmdk": "^1.1.1",

package/dist/assets/storefront/src/app/[locale]/account/approvals/page.tsx

@@ -8,6 +8,7 @@ import { Card, CardContent, CardHeader, CardTitle } from '@/components/ui/card';
 import { ResultOf } from '@/graphql';
 import { Link, redirect } from '@/i18n/navigation';
 import { pinRootLocale } from '@/i18n/server';
+import { splitApprovalRequests } from '@/lib/approvals';
 import { formatDateTime } from '@/lib/format';
 import { getActiveCustomer } from '@/lib/vendure/actions';
 import { client } from '@/lib/vendure/api';
@@ -277,14 +278,11 @@ async function ApprovalsContent({ params }: { params: Promise<{ locale: string }
         );
     }
 
-    // Categorize: requests where I have a pending decision vs everything else.
-    // A request with no decisions yet (workflow still initializing) is treated as
-    // pending if the status is PENDING or IN_PROGRESS and I'm not the requester,
-    // since it likely hasn't assigned approvers yet.
-    const pendingApprovals = allRequests.filter((r) =>
-        r.decisions?.some((d) => d.decision === 'PENDING' && d.customer?.id === activeCustomer.id),
+    // Pending: open requests where I still have a pending decision. Everything else is history.
+    const { pending: pendingApprovals, history: pastAndOther } = splitApprovalRequests(
+        allRequests,
+        activeCustomer.id,
     );
-    const pastAndOther = allRequests.filter((r) => !pendingApprovals.includes(r));
 
     // Only fetch order summaries for pending approvals (history rows don't need them)
     const orderMap = await fetchOrderSummaries(pendingApprovals);

package/dist/assets/storefront/src/lib/approvals.ts

@@ -0,0 +1,32 @@
+import type { ResultOf } from '@/graphql';
+import type { GetMyApprovalRequestsQuery } from '@/lib/vendure/queries';
+
+type ApprovalRequest = NonNullable<
+    ResultOf<typeof GetMyApprovalRequestsQuery>['myApprovalRequests']
+>['items'][number];
+
+export type ApprovalRequestStatus = ApprovalRequest['status'];
+export type ApprovalDecisionValue = ApprovalRequest['decisions'][number]['decision'];
+
+interface ApprovalRequestLike {
+    status: ApprovalRequestStatus;
+    decisions?: Array<{ decision: ApprovalDecisionValue; customer?: { id: string } | null }> | null;
+}
+
+/**
+ * Splits requests into those the customer can still decide and the rest.
+ * Mirrors `canDecide` in approval-workflows: the request is open (PENDING or IN_PROGRESS)
+ * and the customer has a PENDING decision. A resolved request can keep PENDING decisions
+ * that its workflow no longer reads, so the status check is required.
+ */
+export function splitApprovalRequests<T extends ApprovalRequestLike>(
+    requests: T[],
+    customerId: string,
+): { pending: T[]; history: T[] } {
+    const pending = requests.filter(
+        (r) =>
+            (r.status === 'PENDING' || r.status === 'IN_PROGRESS') &&
+            r.decisions?.some((d) => d.decision === 'PENDING' && d.customer?.id === customerId),
+    );
+    return { pending, history: requests.filter((r) => !pending.includes(r)) };
+}

package/dist/assets/templates/AGENTS.md.hbs

@@ -38,7 +38,7 @@ docker compose up -d
 Run `npx vendure dev` or `bunx vendure dev` from the workspace root or inside
 `server/`. Both select the server project and its linked development credential.
 From the root, `vendure dev --project server` selects the server explicitly.
-Core loads the Platform CLI plugin from `server/package.json`.
+The Vendure CLI loads the Platform CLI plugin from `server/package.json`.
 
 ## Production commands
 

package/dist/assets/templates/README.md.hbs

@@ -31,14 +31,14 @@ The storefront will be available at `http://localhost:3001`.
 Run `npx vendure dev` or `bunx vendure dev` from the workspace root or inside
 `server/`. Both select the server project and its linked development credential.
 From the root, `vendure dev --project server` selects the server explicitly.
-Core loads the Platform CLI plugin from `server/package.json`.
+The Vendure CLI loads the Platform CLI plugin from `server/package.json`.
 Changes under `src/gql/` in the server project do not restart the server or worker.
 
 ## Updating packages
 
-Update `@vendure/*` and `@vendure-platform/*` together. Core packages use an exact
+Update `@vendure/*` and `@vendure-platform/*` together. Vendure Framework packages use an exact
 version pin. Before an upgrade, set all existing `@vendure/*` entries in the root
-and `server/package.json` to the same compatible Core build. Update both Core CLI
+and `server/package.json` to the same compatible Vendure Framework build. Update both Vendure CLI
 entries. Then run from the workspace root:
 
 | Package manager | Command |
@@ -47,7 +47,7 @@ entries. Then run from the workspace root:
 | Bun | `bun update --recursive` |
 | pnpm | `pnpm --recursive --include-workspace-root update` |
 
-A plain root `bun update` can update Platform release tags while keeping Core at
+A plain root `bun update` can update Platform release tags while keeping the Vendure Framework at
 its locked server-workspace version. Review and commit the updated manifests and
 lockfile together. See the [Platform upgrade guide](https://docs.vendure.io/vendure-platform/platform/upgrading)
 for older scaffolds and verification steps.

package/dist/assets/templates/bunfig.toml.hbs

@@ -5,13 +5,13 @@
 # seconds ago. The default `0` is fine for most projects, but if you (or your
 # org's global `~/.bunfig.toml`) sets it to e.g. `604800` (7 days), then
 # `@vendure-platform/*` releases would be blocked for a week after each
-# Vendure Platform ship. A Platform release can also pin a Core release of
+# Vendure Platform ship. A Platform release can also pin a Vendure Framework release of
 # the same day. The excludes list below bypasses the check for every
-# Vendure Platform and Vendure Core package this scaffold consumes
+# Vendure Platform and Vendure Framework package this scaffold consumes
 # (directly or transitively), so a fresh `bun install` works immediately
-# after a release. Core means `@vendure/*` plus the `@vendure-io/*`
+# after a release. Vendure Framework means `@vendure/*` plus the `@vendure-io/*`
 # packages of the Dashboard. Bun 1.4.2 matches each entry by exact package
-# name and does not expand `@vendure/*`, so add a new Core package here by
+# name and does not expand `@vendure/*`, so add a new Vendure Framework package here by
 # name. The age rule still applies to every other package.
 #
 # See https://bun.com/docs/runtime/bunfig#install-minimumreleaseage

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@vendure-platform/create",
-    "version": "1.0.1",
+    "version": "1.0.2-nightly.202610261747.151.1",
     "description": "CLI tool to scaffold a Vendure demo project with Vendure Platform plugins",
     "vendurePlugin": {
         "slug": "create",
@@ -50,8 +50,8 @@
     "dependencies": {
         "@clack/prompts": "^0.10.0",
         "@vendure/cli": "3.8.0",
-        "@vendure-platform/console-auth": "1.0.1",
-        "@vendure-platform/plugin-meta": "1.0.1",
+        "@vendure-platform/console-auth": "1.0.2-nightly.202610261747.151.1",
+        "@vendure-platform/plugin-meta": "1.0.2-nightly.202610261747.151.1",
         "commander": "^13.1.0",
         "fs-extra": "^11.3.0",
         "handlebars": "^4.7.8",