feat(core-flows,dashboard,js-sdk,promotion,medusa,types,utils): limit promotion usage per customer (#13451)
**What** - implement promotion usage limits per customer/email - fix registering spend usage over the limit - fix type errors in promotion module tests **How** - introduce a new type of campaign budget that can be defined by an attribute such as customer id or email - add `CampaignBudgetUsage` entity to keep track of the number of uses per attribute value - update `registerUsage` and `computeActions` in the promotion module to work with the new type - update `core-flows` to pass context needed for usage calculation to the promotion module **Breaking** - registering promotion usage now throws (and cart complete fails) if the budget limit is exceeded or if the cart completion would result in a breached limit --- CLOSES CORE-1172 CLOSES CORE-1173 CLOSES CORE-1174 CLOSES CORE-1175 Co-authored-by: Adrien de Peretti <25098370+adrien2p@users.noreply.github.com>
This commit is contained in:
@@ -38,6 +38,8 @@ export enum PromotionRuleOperator {
|
||||
export enum CampaignBudgetType {
|
||||
SPEND = "spend",
|
||||
USAGE = "usage",
|
||||
USE_BY_ATTRIBUTE = "use_by_attribute",
|
||||
SPEND_BY_ATTRIBUTE = "spend_by_attribute",
|
||||
}
|
||||
|
||||
export enum ComputedActions {
|
||||
|
||||
@@ -1,5 +1,8 @@
|
||||
import { BigNumberInput } from "@medusajs/types"
|
||||
import { ApplicationMethodAllocation, ApplicationMethodType, } from "../../promotion"
|
||||
import {
|
||||
ApplicationMethodAllocation,
|
||||
ApplicationMethodType,
|
||||
} from "../../promotion"
|
||||
import { MathBN } from "../math"
|
||||
import { MEDUSA_EPSILON } from "../big-number"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user