All checks were successful
构建并部署到测试环境(无 SSH) / build-and-deploy (push) Successful in 7m19s
- 新增迁移 000129:tb_package_usage 添加 paid_amount BIGINT 字段,存量数据通过 JOIN tb_order 回填 - PackageUsage Model 新增 PaidAmount *int64 字段 - 4 个写入点(order service 主套餐/加油包、auto_purchase 主套餐/加油包)赋值 order.ActualPaidAmount - AssetPackageResponse DTO 新增 paid_amount 字段 - GetCurrentPackage / GetPackages 填充 paid_amount,接口直接返回购买价格无需 JOIN 订单表
2.5 KiB
2.5 KiB
package-usage-paid-amount-snapshot Specification
Purpose
在套餐使用记录(tb_package_usage)创建时,快照购买该套餐对应订单的实付金额,使资产套餐接口能直接返回购买价格,无需 JOIN 订单表。
Requirements
Requirement: 套餐使用记录快照实付金额
系统 SHALL 在创建 PackageUsage 记录时,将购买该套餐对应订单的实付金额(tb_order.actual_paid_amount)快照至 tb_package_usage.paid_amount 字段,单位为分(人民币)。
字段规范:
- 数据库字段:
paid_amount BIGINT NULLABLE - Go 字段:
PaidAmount *int64(单位:分) - 赋值来源:
order.ActualPaidAmount,直接赋值,不转换 - 为 null 的情况:线下支付(无实际收款)或无订单关联的企业分配套餐
覆盖范围(所有 PackageUsage 写入点):
internal/service/order/service.goactivateMainPackage()internal/service/order/service.goactivateAddonPackage()internal/task/auto_purchase.goactivateMainPackage()internal/task/auto_purchase.goactivateAddonPackage()
存量数据:通过迁移 SQL UPDATE tb_package_usage SET paid_amount = o.actual_paid_amount FROM tb_order o WHERE pu.order_id = o.id AND pu.order_id != 0 回填,order_id = 0 的记录保持 null。
Scenario: 钱包支付套餐激活时快照实付金额
- WHEN 用户以钱包支付购买套餐,订单
actual_paid_amount = 9900(分) - THEN 激活生成的
PackageUsage.paid_amount = 9900
Scenario: 微信支付回调后激活套餐时快照实付金额
- WHEN 微信支付回调触发
HandlePaymentCallback,actual_paid_amount = 19900,随后调用activatePackage - THEN 生成的
PackageUsage.paid_amount = 19900
Scenario: 线下支付套餐激活时 paid_amount 为 null
- WHEN 管理员以线下支付方式为客户激活套餐,
order.actual_paid_amount = nil - THEN
PackageUsage.paid_amount = nil,接口响应中paid_amount字段缺省(omitempty)
Scenario: 自动购包任务激活套餐时快照实付金额
- WHEN C 端钱包充值触发
auto_purchase任务,自动购买套餐,扣款paidAmount = 5900 - THEN 激活生成的
PackageUsage.paid_amount = 5900
Scenario: 加油包激活时独立快照实付金额
- WHEN 用户购买加油包,对应订单
actual_paid_amount = 2900 - THEN 加油包
PackageUsage.paid_amount = 2900,与主套餐的paid_amount相互独立