32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
# task +complete
|
|
|
|
> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
|
|
|
|
Mark a task as completed.
|
|
|
|
## Recommended Commands
|
|
|
|
```bash
|
|
# Complete a task
|
|
lark-cli task +complete --task-id "<task_guid>"
|
|
|
|
# A task applink is accepted directly; the CLI extracts its guid query value
|
|
lark-cli task +complete --task-id "https://applink.larksuite.com/client/todo/task?guid=<task_guid>"
|
|
```
|
|
|
|
## Parameters
|
|
|
|
| Parameter | Required | Description |
|
|
|-----------|----------|-------------|
|
|
| `--task-id <guid-or-applink>` | Yes | Task OpenAPI GUID or a task applink containing `guid=`. Display task IDs such as `t104121` / `suite_entity_num` are rejected. |
|
|
|
|
## Workflow
|
|
|
|
1. Confirm the task to complete.
|
|
2. Execute the command.
|
|
3. Read `data.status`, `data.completed_at`, and `data.already_completed` from the result. `already_completed: true` means the shortcut observed an already-completed task and skipped the PATCH.
|
|
4. Do not routinely call `task tasks get` when the result already reports `status: done` and a non-zero `completed_at`. Query details only if confirmation fields are absent or the user explicitly asks for a full verification.
|
|
|
|
> [!CAUTION]
|
|
> This is a **Write Operation** -- You must confirm the user's intent before executing.
|