ooodc a7883dbed9 refactor(todo): 重构待办事项管理逻辑及更新状态规则

- 移除 TodoItem 中的 priority、created_at 和 updated_at 字段
- 强制每个任务都必须有唯一 id，且由用户负责生成
- 修改合并模式逻辑，merge=true 下保留未提及的旧任务
- 支持已完成和已取消任务重新激活（状态改回 pending 或 in_progress）
- 禁止 in_progress 状态退回到 pending，必须标记为 completed 或 cancelled
- 优化状态转换校验，允许特定状态间合法切换
- 简化任务变更消息，移除详细的新增/更新/移除统计
- 更新文档和示例，明确 id 必须由用户生成和使用
- 修复和补充测试，增强状态转换和合并模式验证
- 调整任务时间戳生成逻辑，统一使用当前时间及索引
- 该变更提供更合理的任务状态机械及管理模式，提升稳定性和易用性

2026-06-13 09:22:33 +08:00

2.8 KiB

Raw Blame History

lark-wiki +member-remove

Remove a member from a wiki space. OpenAPI: DELETE /open-apis/wiki/v2/spaces/:space_id/members/:member_id. Unlike most DELETEs, this endpoint requires a body carrying member_type and member_role — the :member_id path segment alone is ambiguous without both.

The underlying members.delete API is flagged danger: true in the schema browser, but the operation is recoverable — call +member-add with the same (member_id, member_type, member_role) to restore. No --yes gate.

Usage

lark-cli wiki +member-remove \
  --space-id <space_id> \
  --member-id <open_id|email|user_id|app_id|...> \
  --member-type <openid|email|userid|unionid|openchat|opendepartmentid|appid> \
  --member-role <admin|member> \
  [--as user|bot]

# Personal library (resolves my_library first)
lark-cli wiki +member-remove \
  --space-id my_library \
  --member-id ou_xxx --member-type openid --member-role member \
  --as user

# Preview the call chain without deleting
lark-cli wiki +member-remove \
  --space-id <id> --member-id <id> --member-type openid --member-role admin \
  --dry-run

Flags

Flag	Type	Required	Default	Description
`--space-id`	string	Yes	—	Wiki space ID; use `my_library` for the personal document library (user only)
`--member-id`	string	Yes	—	Member ID; interpretation is decided by `--member-type`
`--member-type`	enum	Yes	—	Must match the original grant: `openchat` / `userid` / `email` / `opendepartmentid` / `openid` / `unionid` / `appid`
`--member-role`	enum	Yes	—	Must match the original grant: `admin` / `member`
`--as`	enum	No	`auto`	Identity `user`/`bot`; wiki is user-centric → pass `--as user`

Output

{
  "space_id": "7160145948494381236",
  "member_id": "ou_449b53ad6aee526f7ed311b216aabcef",
  "member_type": "openid",
  "member_role": "admin"
}

If the API ever omits the member echo, the CLI falls back to surfacing the caller-supplied (member_id, member_type, member_role) so scripts still see what was removed.

Notes

--member-type and --member-role must match the original grant. Revoking a non-existent (member_id, type, role) tuple is a no-op error from the API. If you do not know the current role, run +member-list first.
Role switch is not a single update. To move someone between admin and member, call +member-remove with the old role first, then +member-add with the new one.
Bot + my_library is rejected upfront. Pass an explicit --space-id when --as bot.
--dry-run previews 2 steps when --space-id my_library (resolve → delete), 1 step otherwise.

Required Scope

wiki:member:update

2.8 KiB Raw Blame History