mirror of
https://github.com/hansjone/dsh-im-ops.git
synced 2026-10-11 00:32:43 +08:00
3b810fea6b
Regular answers reuse the stream card, which is created through the
reply API targeting the triggering message, so they land in the right
Feishu thread. Pending Harness questions (ask_user_question) were sent
through a fresh message.create with only the chat_id, so in topic
groups they appeared in the group's default area instead of the topic
the conversation belongs to.
Thread question delivery the same way as answers:
- #send accepts { replyTo } and uses im.v1.message.reply, falling back
to a plain message when the referenced one is gone
- the triggering message id now travels into the interaction context
and pending state, and #presentInteraction replies to it
- resolved-question notices reply to the user's answer message
- bridge.test.mjs: assert the question is delivered via the reply API
targeting the triggering message inside a topic group
- lib/index.js: regenerated host bundle
|
||
|---|---|---|
| .. | ||
| fixtures | ||
| bridge.test.mjs | ||
| client-api.test.mjs | ||
| config.test.mjs | ||
| connection-supervisor.test.mjs | ||
| connection-test-client.test.mjs | ||
| feishu-app.test.mjs | ||
| feishu-cards.test.mjs | ||
| feishu-channel.test.mjs | ||
| feishu-proxy.test.mjs | ||
| feishu-runtime.test.mjs | ||
| group-message-permission-manager.test.mjs | ||
| harness-client.test.mjs | ||
| lark-sdk-handshake-patch.test.mjs | ||
| message-utils.test.mjs | ||
| multi-bot-controller.test.mjs | ||
| plugin-config-store.test.mjs | ||
| plugin-controller.test.mjs | ||
| plugin-host.test.mjs | ||
| registration-manager.test.mjs | ||
| repair-manager.test.mjs | ||
| slash-command-registry.test.mjs | ||
| state-store.test.mjs | ||