hailin
/
rwadurian
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2,643 Commits 1 Branch 10 Tags 184 MiB
Commit Graph

12 Commits

Author SHA1 Message Date
hailin a55201b3b3 feat(referral+mobile): 功能6 — App 团队预种数量展示 
纯新增实现，不修改任何现有业务逻辑，对现有系统零风险。

## 后端 — referral-service

新建 TeamPrePlantingController（JWT 认证），2 个公开端点：

1. GET /referral/me/team-pre-planting
   - 返回当前用户的个人预种份数、团队预种总量
   - 返回直推成员列表及每人的预种份数
   - 从 TeamStatistics 表读取（CDC 事件维护的数据）

2. GET /referral/me/team-pre-planting/members?limit=20&offset=0
   - 分页返回全部团队成员的预种明细（仅有预种份数 > 0 的成员）
   - 使用 ancestor_path 数组查询所有下级用户
   - JOIN team_statistics 获取每人的 selfPrePlantingPortions

Kong 网关无需修改（/api/v1/referral/* 已覆盖）。

## 前端 — Flutter mobile-app

新建 TeamPrePlantingPage 页面：
- 顶部统计卡片：个人预种 + 团队预种总量
- 直推预种明细列表（所有用户可见）
- 全部团队成员预种明细（仅市/省公司管理者可见，分页加载更多）
- 普通用户看到锁定提示"仅市公司/省公司管理者可查看"

入口：个人中心页预种按钮行新增绿色「团队预种」按钮。

## 文件清单

新建文件：
- backend/.../controllers/team-pre-planting.controller.ts（核心后端控制器）
- frontend/.../pages/team_pre_planting_page.dart（Flutter 团队预种页面）

微量修改（仅追加新行）：
- controllers/index.ts: +1 行 export
- api.module.ts: +2 行 import/注册
- api_endpoints.dart: +2 行端点常量
- referral_service.dart: +4 模型类 +2 API 方法
- route_paths.dart, route_names.dart: +1 行路由定义
- app_router.dart: +1 import +1 GoRoute
- profile_page.dart: 预种按钮行追加第三个按钮

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-03-02 07:15:17 -08:00
hailin ac15d6682a feat(admin): 用户预种数量展示 & 授权申请照片查看 
## 功能7：用户管理展示预种数量

### 需求
在用户管理（列表+详情页）展示个人及团队预种份数，
并支持跳转预种管理页查看团队中哪些ID购买了预种。

### 后端变更

referral-service — 新增内部 API:
  - GET  /internal/referral/pre-planting-stats/:accountSequence
  - POST /internal/referral/pre-planting-stats/batch
  从 TeamStatistics 表查询 selfPrePlantingPortions/teamPrePlantingPortions

admin-service:
  - 新建 ReferralProxyService (src/referral/) 代理 referral-service 内部 API
  - UserFullDetailDto 新增 selfPrePlantingPortions, teamPrePlantingPortions
  - user-detail.controller 并行调用获取预种统计
  - user.controller 批量获取用户列表预种统计
  - UserListItemDto 新增 selfPrePlantingPortions, teamPrePlantingPortions
  - pre-planting-config.controller 新增 teamOf 查询参数
    → 先从 referralQueryView 获取团队成员列表
    → 将 accountSequences 传递给 planting-service 过滤

planting-service:
  - internal-pre-planting.controller 的 admin orders/positions 端点
    新增 accountSequences 查询参数，支持按用户列表过滤

### 前端变更

admin-web:
  - 用户列表页表格新增"个人预种(份)"、"团队预种(份)"两列
  - 用户详情页新增预种统计卡片（个人/团队预种份数）
  - 团队预种数字可点击，跳转 /pre-planting?teamOf={accountSequence}
  - 预种管理页支持 teamOf URL 参数，团队过滤模式下显示提示条+返回链接

---

## 功能8：授权管理查看申请照片

### 需求
管理后台无法查看社区/市公司/省公司申请时提供的办公室照片。
原因：authorization-service 收到 officePhotoUrls 后只验证未持久化。
照片文件本身已存储在 MinIO，只需持久化 URL 到数据库。

### 后端变更

authorization-service:
  - schema.prisma: AuthorizationRole 新增 officePhotoUrls String[] 字段
  - authorization-role.aggregate: props/字段/getter/构造/toPersistence/所有工厂方法
  - repository: save() create/update 块 + toDomain() 映射
  - application service: 3个 self-apply 方法传递 officePhotoUrls 到 aggregate
  - admin controller: queryAuthorizations 响应包含 officePhotoUrls

admin-service:
  - schema.prisma: AuthorizationRoleQueryView 新增 officePhotoUrls 字段
  - user-detail-query.repository 接口 + impl: 包含 officePhotoUrls
  - user-detail.dto: AuthorizationRoleDto 新增 officePhotoUrls

### 前端变更

admin-web:
  - 授权管理页表格新增"申请照片"列，点击弹出照片网格 Modal
  - 照片支持点击放大（全屏 lightbox 覆盖层）
  - 用户详情页授权信息 Tab 同样支持查看照片
  - authorization.types.ts / userDetail.types.ts 类型更新

---

## 部署注意事项
1. authorization-service 需运行: npx prisma migrate dev --name add-office-photo-urls
2. admin-service 需运行: npx prisma migrate dev --name add-auth-role-office-photos
3. 需部署: authorization-service, admin-service, referral-service, planting-service, admin-web

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-03-02 03:09:17 -08:00
hailin b3a3652f21 feat(transfer): 树转让功能全量实现（纯新增，零侵入） 
实现已认种果树所有权在用户间转让的完整功能。采用方案一：
独立 transfer-service 微服务 + Saga 编排器模式。

=== 架构设计 ===
- Saga 编排器 8 步正向流程：卖方确认 → 冻结资金 → 锁定树 →
  变更所有权 → 调整算力 → 更新统计 → 结算资金 → 完成
- 补偿回滚：任一步骤失败自动反向补偿（解冻资金 → 解锁树）
- 13 种状态：PENDING → SELLER_CONFIRMED → PAYMENT_FROZEN →
  TREES_LOCKED → OWNERSHIP_TRANSFERRED → CONTRIBUTION_ADJUSTED →
  STATS_UPDATED → PAYMENT_SETTLED → COMPLETED / CANCELLED /
  FAILED / ROLLING_BACK / ROLLED_BACK

=== Phase 1-2: transfer-service（独立微服务） ===
新建文件：
- Prisma Schema：transfer_orders + transfer_status_logs + outbox_events
- Domain：TransferOrder 聚合根 + TransferFeeService（5% 手续费）
- Application：TransferApplicationService + SagaOrchestratorService
- Infrastructure：Kafka 事件消费/生产 + Outbox Pattern
- API：TransferController（用户端）+ AdminTransferController（管理端）
- External Clients：wallet/planting/identity-service HTTP 客户端
- Docker + 环境配置

=== Phase 3: 现有微服务扩展（纯追加） ===
planting-service：
- Prisma schema 追加 transferLockId 可空字段
- InternalTransferController：锁定/解锁/执行 3 个新端点
- Kafka handlers：transfer-lock/execute/rollback 事件处理
- main.ts 追加 Kafka consumer group 配置

referral-service：
- PlantingTransferredHandler：处理转让后团队统计更新
- TeamStatisticsAggregate 追加 handleTransfer() 方法
- TeamStatisticsRepository 追加 adjustForTransfer() 方法
- ProvinceCityDistribution 追加 transferTrees() 方法

contribution-service：
- TransferOwnershipHandler：处理所有权变更事件
- TransferAdjustmentService：算力调整（879 行核心逻辑）
- Prisma schema 追加 transferOrderId 可空字段
- ContributionAccount 追加 applyTransferAdjustment() 方法

=== Phase 4A: wallet-service（3 个新内部端点） ===
新建文件：
- FreezeForTransferDto / UnfreezeForTransferDto / SettleTransferDto
- FreezeForTransferCommand / UnfreezeForTransferCommand / SettleTransferPaymentCommand
- InternalTransferWalletController（POST freeze/unfreeze/settle-transfer）

修改文件：
- wallet-application.service.ts 追加 3 组方法（+437 行）：
  freezeForTransfer / unfreezeForTransfer / settleTransferPayment
  （乐观锁 + 3 次重试 + Prisma $transaction + 幂等检查）
- 结算操作：单事务内更新 3 个钱包（买方扣减 + 卖方入账 + 手续费归集）

=== Phase 4B: admin-web（转让管理页面） ===
新建文件：
- transferService.ts：API 调用服务 + 完整类型定义
- useTransfers.ts：React Query hooks（list/detail/stats/forceCancel）
- /transfers/page.tsx：列表页（统计卡片 + 搜索筛选 + 分页 + 13 种状态 badge）
- /transfers/[transferOrderNo]/page.tsx：详情页（Saga 时间线 + 状态日志 + 强制取消）
- transfers.module.scss：完整样式

修改文件：
- endpoints.ts 追加 TRANSFERS 端点配置
- Sidebar.tsx 追加「转让管理」菜单项
- hooks/index.ts 追加 useTransfers 导出

=== Phase 4C: mobile-app（转让 UI） ===
新建文件：
- transfer_service.dart：Flutter API 服务 + Model（TransferOrder/Detail/StatusLog）
- transfer_list_page.dart：转让记录列表（全部/转出/转入 Tab + 下拉刷新）
- transfer_detail_page.dart：转让详情（Saga 时间线 + 确认/取消操作）
- transfer_initiate_page.dart：发起转让表单（手续费自动计算）

修改文件：
- injection_container.dart 追加 transferServiceProvider
- route_paths.dart + route_names.dart 追加 3 个路由
- app_router.dart 追加 3 个 GoRoute
- profile_page.dart 追加「发起转让」+「转让记录」按钮行

=== 基础设施 ===
- docker-compose.yml 追加 transfer-service 容器配置
- deploy.sh 追加 transfer-service 部署
- init-databases.sh 追加 transfer_db 数据库初始化

=== 纯新增原则 ===
所有变更均为追加式修改，不修改任何现有业务逻辑：
- 新增 nullable 字段（不影响现有数据）
- 新增 enum 值（不影响现有枚举使用）
- 新增 providers/controllers（不影响现有依赖注入）
- 新增页面/路由（不影响现有页面行为）

回滚方式：删除 transfer-service 目录 + 移除各服务中带 [2026-02-19] 标记的代码

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-02-19 03:44:02 -08:00
hailin 714ce42e4f feat(contract-signing): 添加电子合同签署功能及单点配置优化 
- planting-service: 添加合同签署任务管理和超时检测
  - 新增 ContractSigningTask 领域模型
  - 添加 24 小时合同签署超时定时任务
  - 支付后资金保持冻结，由 referral-service 统一确认扣款

- referral-service: 单点配置 CONTRACT_SIGNING_ENABLED
  - 新增 ContractSigningHandler 处理合同签署/超时事件
  - 新增 WalletServiceClient 调用钱包服务确认扣款
  - planting.created 处理后根据配置决定是否等待合同签署

- reward-service: 移除 CONTRACT_SIGNING_ENABLED 配置
  - 扣款确认由 referral-service 在发送事件前完成
  - 保持奖励分配逻辑不变

配置说明:
- CONTRACT_SIGNING_ENABLED=true (默认): 等待合同签署后分配奖励
- CONTRACT_SIGNING_ENABLED=false: 立即分配奖励（原有流程）

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2025-12-24 20:12:12 -08:00
hailin 1a5925494e feat(referral): integrate authorization-service for community/province/city rights allocation 
## Problem
社区/省/市权益分配一直返回 null，导致所有权益都分配给系统账户而非正确的授权用户。
原因：referral-service 的 getReferralContext 接口中 nearestCommunity、nearestProvinceAuth、
nearestCityAuth 三个字段硬编码为 null，注释说"需要后续实现"但一直未实现。

## Solution
1. 新建 AuthorizationServiceClient 调用 authorization-service 的内部 API
   - /api/v1/authorization/nearest-community
   - /api/v1/authorization/nearest-province
   - /api/v1/authorization/nearest-city
2. 修改 InternalReferralController 使用并行查询获取授权信息
3. 添加 fallback 机制：authorization-service 不可用时返回 null（保持现有行为）
4. docker-compose.yml 添加 AUTHORIZATION_SERVICE_URL 环境变量

## Files Changed
- backend/services/referral-service/src/infrastructure/external/authorization-service.client.ts (new)
- backend/services/referral-service/src/api/controllers/referral.controller.ts
- backend/services/referral-service/src/modules/infrastructure.module.ts
- backend/services/docker-compose.yml

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2025-12-11 02:10:33 -08:00
hailin 9cf8b5305b feat(authorization): add community hierarchy API 
- Add internal referral-chain API in referral-service for getting ancestor path and team members
- Extend ReferralServiceClient to call referral-chain API
- Add findActiveCommunityByAccountSequences repository method
- Add getCommunityHierarchy application service method
- Add GET /authorizations/my/community-hierarchy endpoint
- Update frontend with CommunityHierarchy model and getMyCommunityHierarchy method

API returns:
- myCommunity: user's own community authorization (if any)
- parentCommunity: nearest parent community (defaults to 总部社区 if none)
- childCommunities: nearest child communities in user's team

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2025-12-10 18:18:49 -08:00
hailin ccef23f5b0 feat(authorization): integrate with referral-service for team statistics 
- Add InternalTeamStatisticsController in referral-service for service-to-service API
- Create ReferralServiceClient in authorization-service to fetch real team statistics
- Replace MockTeamStatisticsRepository with real HTTP client implementation
- Configure docker-compose with REFERRAL_SERVICE_URL for authorization-service

This enables authorization-service to get real team planting counts from
referral-service for authorization assessment and activation logic.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2025-12-10 16:30:35 -08:00
hailin 807dc8705d fix(referral): add EventAckPublisher to InfrastructureModule 
- Refactor EventAckPublisher to use KafkaService instead of ClientKafka
- Add kafka/index.ts export file
- Register EventAckPublisher in InfrastructureModule providers and exports

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2025-12-09 22:29:54 -08:00
hailin 2bf5ca933e refactor(referral): remove legacy leaderboard code 
Remove duplicate leaderboard functionality from referral-service.
All leaderboard features should now go through leaderboard-service.

Removed files:
- api/controllers/leaderboard.controller.ts
- api/dto/leaderboard.dto.ts
- application/queries/get-leaderboard.query.ts
- infrastructure/cache/leaderboard-cache.service.ts
- Related test files

Modified:
- TeamStatisticsService: removed getLeaderboard() and getUserRank()
- Module registrations updated

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2025-12-09 22:05:48 -08:00
hailin 781721a659 feat(withdrawal): implement withdrawal order and fund allocation system 
- Add SystemAccount domain in authorization-service for managing regional/company accounts
- Implement fund allocation service in planting-service with multi-tier distribution
- Add WithdrawalOrder aggregate in wallet-service with full lifecycle management
- Create internal wallet controller for cross-service fund allocation
- Add Kafka event publishing for withdrawal requests
- Implement unit-of-work pattern for transactional consistency
- Update Prisma schemas with withdrawal order and system account tables

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-12-09 02:35:27 -08:00
hailin 747e4ae8ef refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing 
- Remove Address field from PartyEndpoint (parties connect to router themselves)
- Update K8s Discovery to only manage PartyID and Role labels
- Add Party registration and SessionEvent protobuf definitions
- Implement PartyRegistry and SessionEventBroadcaster domain logic
- Add RegisterParty and SubscribeSessionEvents gRPC handlers
- Prepare infrastructure for party-driven MPC coordination

This is the first phase of migrating from coordinator-driven to party-driven
architecture following international MPC system design patterns.
 2025-12-05 08:11:28 -08:00
Developer 7ae98c7f5b feat(referral-service): Implement complete referral service with DDD architecture 
Implement the referral service microservice with comprehensive features:

## Domain Layer
- ReferralRelationship aggregate: manages user referral relationships
- TeamStatistics aggregate: tracks team statistics and leaderboard scores
- Value Objects: UserId, ReferralCode, ReferralChain, LeaderboardScore, ProvinceCityDistribution
- Domain Services: ReferralChainService, LeaderboardCalculationService
- Domain Events: ReferralRelationshipCreated, TeamStatisticsUpdated

## Application Layer
- ReferralService: create relationships, get user info, validate codes
- TeamStatisticsService: update statistics, get leaderboard, province/city distribution
- Commands: CreateReferralRelationship, UpdateTeamStatistics
- Queries: GetUserReferralInfo, GetDirectReferrals, GetLeaderboard, GetProvinceCityDistribution
- Event Handlers: UserRegisteredHandler, PlantingCreatedHandler

## Infrastructure Layer
- Prisma repositories with PostgreSQL
- Redis caching for leaderboard
- Kafka messaging for domain events
- JWT authentication guard

## API Layer
- REST endpoints for referral management
- Leaderboard endpoints with pagination
- Team statistics endpoints
- Health check endpoints

## Testing (127 unit + 35 integration + 16 E2E tests)
- Domain layer unit tests (100% coverage)
- Integration tests with mocks
- E2E tests with supertest
- Docker test environment with PostgreSQL, Redis, Redpanda

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-12-01 00:18:20 -08:00