Skip to content

fix(qq): use msg_type:2 with markdown wrapper for proper QQ markdown …#47

Closed
zz6zz666 wants to merge 1 commit into
espressif:masterfrom
zz6zz666:pr/fix-qq
Closed

fix(qq): use msg_type:2 with markdown wrapper for proper QQ markdown …#47
zz6zz666 wants to merge 1 commit into
espressif:masterfrom
zz6zz666:pr/fix-qq

Conversation

@zz6zz666
Copy link
Copy Markdown
Contributor

@zz6zz666 zz6zz666 commented May 6, 2026

…rendering

The old msg_type:0 (plain text) caused QQ to display raw markdown syntax instead of rendering it. The new QQ Bot API uses msg_type:2 with a markdown { content } wrapper for proper formatting, matching the official openclaw-qqbot reference implementation.

Description

Related

Testing


Checklist

Before submitting a Pull Request, please ensure the following:

  • 🚨 This PR does not introduce breaking changes.
  • All CI checks (GH Actions) pass.
  • Documentation is updated as needed.
  • Tests are updated or added as necessary.
  • Code is well-commented, especially in complex areas.
  • Git history is clean — commits are squashed to the minimum necessary.

…rendering

The old msg_type:0 (plain text) caused QQ to display raw markdown
syntax instead of rendering it. The new QQ Bot API uses msg_type:2
with a markdown { content } wrapper for proper formatting, matching
the official openclaw-qqbot reference implementation.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented May 8, 2026

CLA assistant check
All committers have signed the CLA.

@laride
Copy link
Copy Markdown
Collaborator

laride commented May 19, 2026

Thanks for the PR! Could you please rebase this PR onto the latest master branch so we can continue processing it?

@Karasukaigan
Copy link
Copy Markdown
Contributor

Karasukaigan commented May 21, 2026

Setting the message type to 2 will cause the QQ and TIM desktop clients to be unable to display messages correctly:

ScreenShot_2026-05-21_144632_378

My solution (#99) is to add a setting option on the frontend, allowing users to decide for themselves whether to display messages in Markdown format.

ScreenShot_2026-05-21_143441_347

@zz6zz666 @laride

@laride
Copy link
Copy Markdown
Collaborator

laride commented May 26, 2026

We have already merged PR #99, which provides similar functionality in a more complete implementation, so we will close this PR.

Thank you for your contribution!

@laride laride closed this May 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants