feat: some
All checks were successful
构建并部署前端到测试环境 / deploy (push) Successful in 55s

This commit is contained in:
luo
2026-09-22 12:14:47 +08:00
parent c136f68ab8
commit 0a28b7d8ef
19 changed files with 608 additions and 117 deletions

View File

@@ -0,0 +1,19 @@
# Change: 对齐业务用户组成员增量管理接口
## Why
《产品迭代8月份/修改.md》已将业务用户组成员维护从“整体替换”调整为增量增加/迁移和按组移除。当前前端仍调用旧 PUT/全局 DELETE 接口,无法展示候选成员归属和操作提示。
## What Changes
- 对齐成员查询、成员候选、增量增加/迁移、按组移除接口。
- 成员管理弹窗展示当前成员及成员关系信息。
- 候选账号展示 `add`、`already_member`、`move` 操作提示。
- 停用组允许查询和移除,但新增/迁移由后端拒绝并提示。
- 用户组列表/详情使用实时成员数。
## Impact
- Affected specs: `business-user-group-management`
- Affected code: business user group types/API/page
- Breaking API alignment: 移除前端对旧整体替换 PUT 与全局清空 DELETE 的调用。

View File

@@ -0,0 +1,17 @@
## ADDED Requirements
### Requirement: Incremental Business User Group Membership
The frontend SHALL use the member query, candidate query, incremental POST add/move, and scoped DELETE remove contracts from the modification document.
#### Scenario: Add or move members
- **WHEN** the user selects candidate accounts and confirms adding members
- **THEN** the frontend MUST POST the account IDs to `/api/admin/business-user-groups/{id}/members`
- **AND** MUST refresh current members and member counts
#### Scenario: Remove current members
- **WHEN** the user selects members currently belonging to the group and confirms removal
- **THEN** the frontend MUST DELETE `/api/admin/business-user-groups/{id}/members` with the account IDs
- **AND** MUST refresh current members

View File

@@ -0,0 +1,14 @@
## 1. Contract
- [ ] 1.1 更新成员、候选和成员数类型。
- [ ] 1.2 更新 `BusinessUserGroupService` 方法与 HTTP 方法/路径。
## 2. UI
- [ ] 2.1 展示当前成员列表和成员状态。
- [ ] 2.2 使用候选接口展示归属筛选和操作提示。
- [ ] 2.3 将“整体替换”改为增量添加/迁移,将移除限定为当前组成员。
## 3. Verification
- [ ] 3.1 运行类型检查、lint、编码检查、构建和 OpenSpec 校验。