Skip to content

Docs: Fix feishu subscription mode description#150

Merged
crispyberry merged 1 commit intomemovai:mainfrom
wjc1207:fix/feishu-md
Mar 16, 2026
Merged

Docs: Fix feishu subscription mode description#150
crispyberry merged 1 commit intomemovai:mainfrom
wjc1207:fix/feishu-md

Conversation

@wjc1207
Copy link
Copy Markdown
Contributor

@wjc1207 wjc1207 commented Mar 14, 2026

Docs: Fix feishu subscription mode description

Summary by CodeRabbit

  • Documentation
    • Updated Feishu integration documentation to reflect transition from HTTP webhook-based event subscription to WebSocket persistent connection mode.
    • Revised setup instructions, architecture diagrams, and API references to align with the new long-connection messaging flow.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 14, 2026

📝 Walkthrough

Walkthrough

Documentation updated to reflect Feishu channel integration using WebSocket persistent connection mode instead of HTTP webhook event subscription. Descriptions of architecture, API references, and setup instructions modified to align with the new connection approach.

Changes

Cohort / File(s) Summary
Feishu Documentation
main/channels/feishu/README.md
Updated event subscription approach from HTTP webhook to WebSocket persistent connection; revised architecture flow, API function descriptions, and related documentation references.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

documentation

Suggested reviewers

  • crispyberry

Poem

🐰 A hop and a skip, the webhooks take flight,
WebSocket connections now hold through the night,
Persistent and steady, the long-connection flows,
From Feishu to ESP32, a better path grows! 🔗✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: updating the Feishu subscription mode description in documentation from webhook to WebSocket persistent connection.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
main/channels/feishu/README.md (1)

55-59: Consider adding a language specifier to the fenced code block.

The architecture diagram accurately depicts the WebSocket-based communication pattern. For markdown lint compliance, consider adding a language specifier (e.g., text or plaintext) to the code fence on line 55.

📝 Proposed fix
-```
+```text
 Feishu Server (wss://open.feishu.cn)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@main/channels/feishu/README.md` around lines 55 - 59, The fenced code block
that contains "Feishu Server (wss://open.feishu.cn)" should include a language
specifier to satisfy markdown linting; edit the opening triple-backtick for that
block (the ``` before "Feishu Server (wss://open.feishu.cn)") and add a language
token such as text or plaintext (e.g., ```text) so the block is explicitly
typed.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@main/channels/feishu/README.md`:
- Around line 55-59: The fenced code block that contains "Feishu Server
(wss://open.feishu.cn)" should include a language specifier to satisfy markdown
linting; edit the opening triple-backtick for that block (the ``` before "Feishu
Server (wss://open.feishu.cn)") and add a language token such as text or
plaintext (e.g., ```text) so the block is explicitly typed.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1dfd6cae-2caa-42a2-9c35-7a03825f58c5

📥 Commits

Reviewing files that changed from the base of the PR and between 5ff0920 and b3fe640.

📒 Files selected for processing (2)
  • main/channels/feishu/README.md
  • main/cli/serial_cli.c

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
main/channels/feishu/README.md (2)

55-69: Architecture diagram accurately reflects WebSocket persistent connection.

The updated architecture clearly shows the WebSocket-based flow with ESP32 initiating the connection, which aligns with the persistent connection mode described in the setup instructions.

Optional: Specify language for code fence to satisfy linter.

The static analysis tool flags the code fence at line 55 for missing a language specification. Consider adding text to satisfy the linter.

🔧 Optional linter fix
-```
+```text
 Feishu Server (wss://open.feishu.cn)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@main/channels/feishu/README.md` around lines 55 - 69, The markdown code fence
in the Feishu architecture diagram lacks a language tag causing the linter
warning; update the fenced block around the ASCII diagram (the block that starts
with "Feishu Server (wss://open.feishu.cn)" in main/channels/feishu/README.md)
to include a language identifier such as text (e.g., change ``` to ```text) so
the linter stops flagging it.

48-51: Consider adding brief UI guidance for setting persistent connection mode.

Step 4 instructs users to "Set subscription mode to Persistent connection" but doesn't specify where in the Feishu platform UI this setting is located. Users unfamiliar with Feishu might benefit from a brief note like "In Event Subscription settings" or similar guidance.

📝 Optional enhancement for clarity
 4. Configure Event Subscription:
-   - Set subscription mode to **Persistent connection** (长连接)
+   - In Event Subscription settings, set subscription mode to **Persistent connection** (长连接)
    - Subscribe to: `im.message.receive_v1`
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@main/channels/feishu/README.md` around lines 48 - 51, Step 4's instruction to
"Set subscription mode to **Persistent connection**" lacks UI context; update
the README's Configure Event Subscription section to briefly show where to
change this in the Feishu console (e.g., open your app in Feishu Developer
Console → Event Subscription settings → set Mode to "Persistent connection
(长连接)"), and explicitly mention subscribing to the `im.message.receive_v1` event
so users know which UI field to update; keep the note short and place it next to
the existing step for clarity.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@main/channels/feishu/README.md`:
- Around line 55-69: The markdown code fence in the Feishu architecture diagram
lacks a language tag causing the linter warning; update the fenced block around
the ASCII diagram (the block that starts with "Feishu Server
(wss://open.feishu.cn)" in main/channels/feishu/README.md) to include a language
identifier such as text (e.g., change ``` to ```text) so the linter stops
flagging it.
- Around line 48-51: Step 4's instruction to "Set subscription mode to
**Persistent connection**" lacks UI context; update the README's Configure Event
Subscription section to briefly show where to change this in the Feishu console
(e.g., open your app in Feishu Developer Console → Event Subscription settings →
set Mode to "Persistent connection (长连接)"), and explicitly mention subscribing
to the `im.message.receive_v1` event so users know which UI field to update;
keep the note short and place it next to the existing step for clarity.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c14a7317-3e58-443f-8bf9-0c5e971c2388

📥 Commits

Reviewing files that changed from the base of the PR and between b3fe640 and 07ca630.

📒 Files selected for processing (1)
  • main/channels/feishu/README.md

Copy link
Copy Markdown
Member

@IRONICBo IRONICBo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@IRONICBo IRONICBo self-assigned this Mar 15, 2026
@IRONICBo IRONICBo added documentation Improvements or additions to documentation ready to merge labels Mar 15, 2026
@crispyberry crispyberry merged commit 9f17f1d into memovai:main Mar 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants