重构用的提案,现在不敢跑
All checks were successful
构建并部署到测试环境(无 SSH) / build-and-deploy (push) Successful in 49s
All checks were successful
构建并部署到测试环境(无 SSH) / build-and-deploy (push) Successful in 49s
This commit is contained in:
@@ -0,0 +1,31 @@
|
||||
## MODIFIED Requirements
|
||||
|
||||
### Requirement: 创建钱包充值订单
|
||||
创建钱包充值订单 SHALL 写入 `tb_recharge_order`(非强充时 linked_package_ids 为 NULL),并同时创建 `tb_payment` 记录。不再写入 `tb_asset_recharge_record`。充值订单号格式保持 CRCH 前缀兼容。
|
||||
|
||||
#### Scenario: 用户主动充值写新表
|
||||
- **WHEN** 用户发起钱包充值(非强充场景)
|
||||
- **THEN** 创建 `tb_recharge_order`(linked_package_ids=NULL,auto_purchase_status=NULL)
|
||||
- **THEN** 创建 `tb_payment`(payment_method=wechat/alipay,status=1)
|
||||
- **THEN** 不写 `tb_asset_recharge_record`
|
||||
|
||||
### Requirement: 充值支付回调处理
|
||||
充值支付回调 SHALL 查 `tb_payment` 获取充值订单,更新 `tb_payment.status=2`,更新 `tb_recharge_order.status=2`,增加钱包余额,创建钱包流水。原有 `RechargeService.HandlePaymentCallback` 中对 `tb_asset_recharge_record` 的操作全部迁移到新表。
|
||||
|
||||
#### Scenario: 充值回调更新新表
|
||||
- **WHEN** 充值支付回调到达
|
||||
- **THEN** 查 `tb_payment` by payment_no
|
||||
- **THEN** 事务:更新 `tb_payment.status=2` → 更新 `tb_recharge_order.status=2` → 增加 `tb_asset_wallet.balance` → 创建 `tb_asset_wallet_transaction`(reference_type=recharge)
|
||||
|
||||
### Requirement: 充值记录新增 auto_purchase_status 状态追踪
|
||||
此需求 SHALL 迁移至 `tb_recharge_order.auto_purchase_status` 字段,语义和状态枚举不变(pending / success / failed)。`tb_asset_recharge_record` 上的该字段随表一起归档停用。
|
||||
|
||||
#### Scenario: 强充后 auto_purchase 完成,更新新表字段
|
||||
- **WHEN** auto_purchase 任务完成套餐激活
|
||||
- **THEN** `tb_recharge_order.auto_purchase_status` 更新为 success(不再更新 `tb_asset_recharge_record`)
|
||||
|
||||
## REMOVED Requirements
|
||||
|
||||
### Requirement: Store 方法签名支持事务参数
|
||||
**Reason**: `AssetRechargeStore` 连同 `tb_asset_recharge_record` 一起删除,其事务方法签名不再需要维护。
|
||||
**Migration**: 事务支持迁移至 `RechargeOrderStore` 和 `PaymentStore`,方法签名设计参考 `recharge-order` spec。
|
||||
Reference in New Issue
Block a user