@amaster.ai/pi-lark 0.1.2-beta.78 → 0.1.2-beta.79
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@amaster.ai/pi-lark",
|
|
3
|
-
"version": "0.1.2-beta.
|
|
3
|
+
"version": "0.1.2-beta.79",
|
|
4
4
|
"description": "Pi extension for Lark/Feishu workspace — calendar, docs, drive, sheets, tasks, mail and more via lark-cli.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
@@ -61,7 +61,7 @@
|
|
|
61
61
|
"vitest": "^4.0.0"
|
|
62
62
|
},
|
|
63
63
|
"dependencies": {
|
|
64
|
-
"@amaster.ai/pi-shared": "0.1.2-beta.
|
|
64
|
+
"@amaster.ai/pi-shared": "0.1.2-beta.79"
|
|
65
65
|
},
|
|
66
66
|
"scripts": {
|
|
67
67
|
"fetch-skills": "node scripts/fetch-skills.mjs",
|
|
@@ -28,6 +28,11 @@ The bot must be the original sender — editing another identity's message fails
|
|
|
28
28
|
| Clear the edited message's attachment zone | `--clear-attachments` | Sets `files:[]` on the post content. Requires a post message; mutually exclusive with `--set-attachments` |
|
|
29
29
|
| Keep the existing attachment zone while rewriting the body | *(no attachment flag)* | **Default.** Editing with only `--markdown` / `--text` / `--content` leaves the current `files` array untouched — a body-only edit never drops attachments |
|
|
30
30
|
|
|
31
|
+
```bash
|
|
32
|
+
# Read the replacement Markdown from a local file
|
|
33
|
+
lark-cli im +messages-edit --as bot --message-id om_xxx --markdown @./updated-message.md
|
|
34
|
+
```
|
|
35
|
+
|
|
31
36
|
## Editing the Attachment Zone
|
|
32
37
|
|
|
33
38
|
`post` messages can carry an attachment zone — a top-level `files` array that renders files/folders under the rich-text body.
|
|
@@ -118,6 +118,9 @@ lark-cli im +messages-reply --message-id om_xxx --markdown $'## Reply\n\n- item
|
|
|
118
118
|
# Reply with a plain one-line message
|
|
119
119
|
lark-cli im +messages-reply --message-id om_xxx --text "Received"
|
|
120
120
|
|
|
121
|
+
# Read Markdown from a local file
|
|
122
|
+
lark-cli im +messages-reply --message-id om_xxx --markdown @./reply.md
|
|
123
|
+
|
|
121
124
|
# Equivalent manual JSON
|
|
122
125
|
lark-cli im +messages-reply --message-id om_xxx --content '{"text":"Received"}'
|
|
123
126
|
|
|
@@ -121,6 +121,9 @@ lark-cli im +messages-send --chat-id oc_xxx --markdown $'## Update\n\n- item 1\n
|
|
|
121
121
|
# Send a plain one-line message
|
|
122
122
|
lark-cli im +messages-send --chat-id oc_xxx --text "Hello"
|
|
123
123
|
|
|
124
|
+
# Read Markdown from a local file
|
|
125
|
+
lark-cli im +messages-send --chat-id oc_xxx --markdown @./update.md
|
|
126
|
+
|
|
124
127
|
# Equivalent manual JSON
|
|
125
128
|
lark-cli im +messages-send --chat-id oc_xxx --content '{"text":"Hello"}'
|
|
126
129
|
|