Files
keysat/licensing-service/migrations/0018_discount_codes_multi_policy.sql
Grant 094cf75e52 v0.2.0:20 — Multi-policy scope for discount codes
A discount code can now apply to a subset of policies on a product
(e.g. "Patron and Pro but not Creator") instead of being limited to
exactly one policy or the entire product.

- Migration 0018 adds `applies_to_policy_ids_json` (nullable JSON array
  of policy ids). Legacy `applies_to_policy_id` stays as the singular
  fallback when the JSON column is empty/NULL.
- `DiscountCode::allowed_policy_ids()` helper unifies multi + singular
  into one Vec. Purchase + preview scope checks consult it.
- `find_applicable_featured_discount` now narrows multi-policy
  candidates in Rust (small candidate set; index-friendly SQL would
  require json_each, deferred).
- Admin API: `POST /v1/admin/discount-codes` accepts `policy_slugs`
  (array) alongside the existing `policy_slug` (singular). Multi wins
  when both are present. PATCH does not allow scope edits — same rule
  as the singular field (disable + recreate to re-scope).
- UI: pill multi-select replaces the policy dropdown on the create
  form. Edit modal's scope label renders the comma-separated list.

UI + schema both back-compat: existing codes keep working unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-11 14:01:51 -05:00

31 lines
1.5 KiB
SQL

-- Migration 0018: multi-policy scope for discount codes
--
-- Until now, a discount code could be scoped to exactly one policy
-- (`applies_to_policy_id`) or "any policy on this product" / global.
-- That left a real gap: "this code is good for Patron OR Pro but not
-- Creator" required creating two distinct codes with different code
-- strings, which is operationally messy.
--
-- New column `applies_to_policy_ids_json`: a JSON-encoded array of
-- policy ids (TEXT uuids). Semantics:
--
-- NULL or '[]' → no multi-policy restriction. Fall back to the legacy
-- `applies_to_policy_id` (single-policy scope) or, if
-- that's also NULL, scope follows `applies_to_product_id`
-- (or global if that's NULL too). Identical behavior
-- to v0.2.0:19 and earlier.
--
-- '["id1","id2",...]' → the code applies if and only if the buyer's
-- chosen policy is in this array. Takes
-- precedence over `applies_to_policy_id` (the
-- legacy singular column is ignored when this
-- is non-empty).
--
-- Migration is purely additive. Existing rows have the new column NULL,
-- so all v0.2.0:19-and-earlier discount codes keep working unchanged.
-- New codes written via the admin API populate this column when the
-- operator picks 2+ policies; single-policy codes continue to write to
-- `applies_to_policy_id` for clarity.
ALTER TABLE discount_codes ADD COLUMN applies_to_policy_ids_json TEXT NULL;