- 移除 TodoItem 中的 priority、created_at 和 updated_at 字段 - 强制每个任务都必须有唯一 id,且由用户负责生成 - 修改合并模式逻辑,merge=true 下保留未提及的旧任务 - 支持已完成和已取消任务重新激活(状态改回 pending 或 in_progress) - 禁止 in_progress 状态退回到 pending,必须标记为 completed 或 cancelled - 优化状态转换校验,允许特定状态间合法切换 - 简化任务变更消息,移除详细的新增/更新/移除统计 - 更新文档和示例,明确 id 必须由用户生成和使用 - 修复和补充测试,增强状态转换和合并模式验证 - 调整任务时间戳生成逻辑,统一使用当前时间及索引 - 该变更提供更合理的任务状态机械及管理模式,提升稳定性和易用性
38 lines
1.4 KiB
Markdown
38 lines
1.4 KiB
Markdown
# task +update
|
|
|
|
> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
|
|
|
|
Update an existing task in Lark.
|
|
|
|
## Recommended Commands
|
|
|
|
```bash
|
|
# Update task summary
|
|
lark-cli task +update --task-id "<task_guid>" --summary "New Summary"
|
|
|
|
# Update multiple tasks' due dates
|
|
lark-cli task +update --task-id "<task_guid>,<another_task_guid>" --due "+2d"
|
|
|
|
# Update with JSON data
|
|
lark-cli task +update --task-id "<task_guid>" --data '{"description": "New description"}'
|
|
```
|
|
|
|
## Parameters
|
|
|
|
| Parameter | Required | Description |
|
|
|-----------|----------|-------------|
|
|
| `--task-id <guid>` | Yes | The task GUID to update. Comma-separated task GUIDs are supported for multiple tasks. For Feishu task applinks, use the `guid` query parameter, not the `suite_entity_num` / display task ID like `t104121`. |
|
|
| `--summary <text>` | No | New summary/title for the task. |
|
|
| `--description <text>` | No | New description for the task. |
|
|
| `--due <time>` | No | New due date (supports relative time). |
|
|
| `--data <json>` | No | JSON payload for fields to update. |
|
|
|
|
## Workflow
|
|
|
|
1. Confirm with the user the tasks to update and the fields.
|
|
2. Execute `lark-cli task +update --task-id "..." ...`
|
|
3. Report the successful updates.
|
|
|
|
> [!CAUTION]
|
|
> This is a **Write Operation** -- You must confirm the user's intent before executing.
|