@doswiftly/storefront-operations 21.0.1 → 22.0.0

package/AGENTS.md

@@ -27,7 +27,7 @@ consumer's `codegen.ts` references this package's `.graphql` files as
 live in the consumer's repo.
 
 <!-- AUTOGEN:STATS:BEGIN — auto-regenerated, do not edit by hand -->
-- **Schema version**: 21.0.1
+- **Schema version**: 22.0.0
 - **Queries**: 52
 - **Mutations**: 44
 - **Fragments**: 105

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 22.0.0
+
+### Major Changes
+
+- 49139e2: Remove the `pendingPoints` field from `LoyaltyPointsSummary` (GraphQL schema, the `LoyaltyPointsSummary` fragment and the generated types). The field was never populated — it always returned `0` — because purchase points are credited directly when the payment is captured, so there is no "pending" state to report.
+
+  **Migration:** if your storefront reads `points.pendingPoints` (or selects `pendingPoints` in a custom query or fragment), remove that usage and re-run your codegen. No replacement field is needed — `currentPoints` has always been the spendable balance.
+
+### Minor Changes
+
+- 49139e2: Referral program signup support — the loyalty referral program now works end-to-end:
+  - `customerSignup` accepts an optional `referralCode` in its input. When the shop's referral program is active, a valid code grants the configured bonus points to the new customer and, after their first paid order, rewards the referrer. An invalid, expired or own code is silently ignored — the signup always succeeds.
+  - New referral capture helpers in the SDK: `useReferralCapture()` / `captureReferralCode()` persist the `?ref=CODE` parameter from a referral landing link into the readable `referral-code` cookie (30 days by default), and `readReferralCodeCookie()` / `clearReferralCodeCookie()` read and clear it at signup time. A server-side `readReferralCodeCookie()` is available from `@doswiftly/storefront-sdk/react/server` for SSR-rendered signup forms. Core constants and the URL extractor (`REFERRAL_COOKIE_NAME`, `REFERRAL_COOKIE_MAX_AGE`, `extractReferralCodeFromUrl`) are exported from the framework-agnostic core entry.
+
+  The cookie lifetime is the _landing → signup_ window and is intentionally independent of the shop's referral validity setting, which starts at signup and is enforced by the API.
+
 ## 21.0.1
 
 ### Patch Changes

package/README.md

@@ -573,7 +573,7 @@ full executable body of each operation.
 | --- | --- | --- |
 | `LoyaltyPageInfo` | `LoyaltyPageInfo` | Page metadata for the loyalty transactions connection (separate type from generic `PageInfo` for legacy reasons; identical shape). |
 | `LoyaltyTier` | `LoyaltyTier` | Loyalty tier definition — name, type enum (`BRONZE` / `SILVER` / `GOLD` / `PLATINUM` / `DIAMOND`), entry threshold (`minPoints` and/or `minAnnualSpend`), points multiplier, custom benefits list. Returned by `loyaltyTiers` and embedded in member tier data. |
-| `LoyaltyPointsSummary` | `LoyaltyPointsSummary` | Customer's points breakdown — total earned, currently spendable, pending (not yet vested), redeemed lifetime, expired lifetime, expiring soon, and the next expiry date. Spread inside `LoyaltyMember`. |
+| `LoyaltyPointsSummary` | `LoyaltyPointsSummary` | Customer's points breakdown — total earned, currently spendable, redeemed lifetime, expired lifetime, expiring soon, and the next expiry date. Spread inside `LoyaltyMember`. |
 | `TierProgress` | `TierProgress` | Customer's progress toward the next tier — current tier, next tier, points + spend remaining, percent progress. Use to render the "X points to GOLD" tracker. |
 | `LoyaltyMember` | `LoyaltyMember` | Customer's loyalty membership — points summary, current tier, tier progress, annual spend, last activity. Returned by `loyaltyMember` (null if not enrolled). |
 | `LoyaltyTransaction` | `LoyaltyTransaction` | One row in the loyalty points history — type (`EARN_PURCHASE` / `EARN_SIGNUP` / `EARN_REFERRAL` / `EARN_REVIEW` / `EARN_BIRTHDAY` / `EARN_BONUS` / `REDEEM` / `EXPIRE` / `ADJUST` / `REFUND_REVERSAL`), points delta, balance after, source order, expiry. Spread on the loyalty dashboard transaction list. |

package/fragments.graphql

@@ -1173,11 +1173,10 @@ fragment LoyaltyTier on LoyaltyTier {
   }
 }
 
-# Customer's points breakdown — total earned, currently spendable, pending (not yet vested), redeemed lifetime, expired lifetime, expiring soon, and the next expiry date. Spread inside `LoyaltyMember`.
+# Customer's points breakdown — total earned, currently spendable, redeemed lifetime, expired lifetime, expiring soon, and the next expiry date. Spread inside `LoyaltyMember`.
 fragment LoyaltyPointsSummary on LoyaltyPointsSummary {
   totalPoints
   currentPoints
-  pendingPoints
   redeemedPoints
   expiredPoints
   expiringPoints

package/llms-full.txt

@@ -1,6 +1,6 @@
 # DoSwiftly Storefront Operations — Full Reference
 
-> Schema version: **21.0.1**
+> Schema version: **22.0.0**
 > 52 queries · 44 mutations · 105 fragments
 
 Auto-generated from `.graphql` source files. Do not edit by hand — this file is
@@ -4311,14 +4311,13 @@ fragment LoyaltyTier on LoyaltyTier {
 
 **Section**: Loyalty Program
 
-**Description**: Customer's points breakdown — total earned, currently spendable, pending (not yet vested), redeemed lifetime, expired lifetime, expiring soon, and the next expiry date. Spread inside `LoyaltyMember`.
+**Description**: Customer's points breakdown — total earned, currently spendable, redeemed lifetime, expired lifetime, expiring soon, and the next expiry date. Spread inside `LoyaltyMember`.
 
 **GraphQL**:
 ```graphql
 fragment LoyaltyPointsSummary on LoyaltyPointsSummary {
   totalPoints
   currentPoints
-  pendingPoints
   redeemedPoints
   expiredPoints
   expiringPoints

package/operations.json

@@ -1,5 +1,5 @@
 {
-  "schemaVersion": "21.0.1",
+  "schemaVersion": "22.0.0",
   "queries": [
     {
       "name": "Shop",
@@ -2777,10 +2777,10 @@
       "name": "LoyaltyPointsSummary",
       "kind": "fragment",
       "section": "Loyalty Program",
-      "description": "Customer's points breakdown — total earned, currently spendable, pending (not yet vested), redeemed lifetime, expired lifetime, expiring soon, and the next expiry date. Spread inside `LoyaltyMember`.",
+      "description": "Customer's points breakdown — total earned, currently spendable, redeemed lifetime, expired lifetime, expiring soon, and the next expiry date. Spread inside `LoyaltyMember`.",
       "variables": [],
       "fragmentRefs": [],
-      "body": "fragment LoyaltyPointsSummary on LoyaltyPointsSummary {\n  totalPoints\n  currentPoints\n  pendingPoints\n  redeemedPoints\n  expiredPoints\n  expiringPoints\n  nextExpiryDate\n}",
+      "body": "fragment LoyaltyPointsSummary on LoyaltyPointsSummary {\n  totalPoints\n  currentPoints\n  redeemedPoints\n  expiredPoints\n  expiringPoints\n  nextExpiryDate\n}",
       "onType": "LoyaltyPointsSummary"
     },
     {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@doswiftly/storefront-operations",
-  "version": "21.0.1",
+  "version": "22.0.0",
   "description": "GraphQL operations for DoSwiftly Storefront - SSOT from backend",
   "homepage": "https://doswiftly.pl",
   "publishConfig": {

package/schema.graphql

@@ -2799,6 +2799,11 @@ input CustomerCreateInput {
 
   """Phone number (free-form)."""
   phone: String
+
+  """
+  Referral code of an existing customer, usually taken from a referral link's `ref` URL parameter (codes are case-insensitive). Optional — an invalid, malformed, expired or own code is silently ignored and the signup still succeeds; only a value longer than 50 characters is rejected. When the shop's referral program is active, a valid code grants the configured bonus points to the new customer and, after their first paid order, rewards the referrer.
+  """
+  referralCode: String
 }
 
 """Customer group for B2B pricing"""
@@ -3771,9 +3776,6 @@ type LoyaltyPointsSummary {
   """Next expiry date (ISO 8601)"""
   nextExpiryDate: DateTime
 
-  """Points pending (from incomplete orders)"""
-  pendingPoints: Int!
-
   """Points redeemed"""
   redeemedPoints: Int!