rwadurian

Commit Graph

Author	SHA1	Message	Date
hailin	4be9c1fb82	refactor!: 重构账户序列号格式 (BREAKING CHANGE) 将 accountSequence 从数字类型改为字符串类型，新格式为: - 普通用户: D + YYMMDD + 5位序号 (例: D2512120001) - 系统账户: S + 10位序号 (例: S0000000001) 主要变更: - identity-service: AccountSequence 值对象改为字符串类型 - identity-service: 序列号生成器改为按日期重置计数 - 所有服务: Prisma schema 字段类型从 BigInt/Int 改为 String - 所有服务: DTO、Command、Event 中的类型定义更新 - Flutter 前端: 相关数据模型类型更新涉及服务: - identity-service (核心变更) - referral-service - authorization-service - wallet-service - reward-service - blockchain-service - backup-service - planting-service - mpc-service - admin-service - mobile-app (Flutter) 注意: 此为破坏性变更，需要清空数据库并重新运行 migration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2025-12-12 09:11:18 -08:00
hailin	d1a7c44f23	fix(referral): correct response parsing for authorization-service API The authorization-service uses TransformInterceptor which wraps all API responses in a standard format: { success, data, timestamp } Before this fix, the AuthorizationServiceClient was reading: response.data.accountSequence (undefined) After this fix, it correctly reads: response.data.data.accountSequence This ensures that nearestCommunity, nearestProvinceAuth, and nearestCityAuth are properly extracted from the wrapped response, allowing community benefits to be correctly allocated to authorized users instead of falling back to SYSTEM_HEADQUARTERS_COMMUNITY. Changes: - Added AuthorizationServiceResponse<T> interface to model wrapped response - Updated findNearestCommunity() to use wrapped response type - Updated findNearestProvince() to use wrapped response type - Updated findNearestCity() to use wrapped response type - Updated catchError handlers to return properly structured fallback data 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2025-12-11 03:08:50 -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

Author

SHA1

Message

Date

hailin

4be9c1fb82

refactor!: 重构账户序列号格式 (BREAKING CHANGE)

将 accountSequence 从数字类型改为字符串类型，新格式为:
- 普通用户: D + YYMMDD + 5位序号 (例: D2512120001)
- 系统账户: S + 10位序号 (例: S0000000001)

主要变更:
- identity-service: AccountSequence 值对象改为字符串类型
- identity-service: 序列号生成器改为按日期重置计数
- 所有服务: Prisma schema 字段类型从 BigInt/Int 改为 String
- 所有服务: DTO、Command、Event 中的类型定义更新
- Flutter 前端: 相关数据模型类型更新

涉及服务:
- identity-service (核心变更)
- referral-service
- authorization-service
- wallet-service
- reward-service
- blockchain-service
- backup-service
- planting-service
- mpc-service
- admin-service
- mobile-app (Flutter)

注意: 此为破坏性变更，需要清空数据库并重新运行 migration

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-12 09:11:18 -08:00

hailin

d1a7c44f23

fix(referral): correct response parsing for authorization-service API

The authorization-service uses TransformInterceptor which wraps all API
responses in a standard format: { success, data, timestamp }

Before this fix, the AuthorizationServiceClient was reading:
  response.data.accountSequence (undefined)

After this fix, it correctly reads:
  response.data.data.accountSequence

This ensures that nearestCommunity, nearestProvinceAuth, and nearestCityAuth
are properly extracted from the wrapped response, allowing community benefits
to be correctly allocated to authorized users instead of falling back to
SYSTEM_HEADQUARTERS_COMMUNITY.

Changes:
- Added AuthorizationServiceResponse<T> interface to model wrapped response
- Updated findNearestCommunity() to use wrapped response type
- Updated findNearestProvince() to use wrapped response type
- Updated findNearestCity() to use wrapped response type
- Updated catchError handlers to return properly structured fallback data

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-11 03:08:50 -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

3 Commits