Skip to content

feat: normalize markdown message send/reply output#28

Merged
liangshuo-1 merged 2 commits intolarksuite:mainfrom
91-enjoy:feat/im_markdown
Mar 30, 2026
Merged

feat: normalize markdown message send/reply output#28
liangshuo-1 merged 2 commits intolarksuite:mainfrom
91-enjoy:feat/im_markdown

Conversation

@91-enjoy
Copy link
Copy Markdown
Contributor

Summary

  • clean up markdown post conversion output for IM send/reply
  • update tests for the new markdown normalization behavior
  • align Skills docs with the implementation

What changed

  • +messages-send and +messages-reply no longer inject literal <br> into markdown-derived post content
  • markdown spacing is normalized with blank lines, and fenced code blocks are preserved without extra wrappers
  • the send/reply Skills docs were updated to match the current --markdown behavior

Test plan

  • run env GOCACHE=/tmp/go-build-cache go test ./...
  • verify the markdown conversion tests cover the updated heading, spacing, and code block output
  • confirm the send/reply Skills describe markdown as normalized post conversion rather than raw markdown passthrough

Change-Id: I6b53eb2207d7c2393d3c7d108df3ba197b9eae46
@91-enjoy 91-enjoy changed the title feat(IM): im markdown send/reply feat(IM): im markdown message send/reply Mar 28, 2026
@91-enjoy 91-enjoy changed the title feat(IM): im markdown message send/reply feat(IM): markdown message send/reply Mar 28, 2026
@91-enjoy 91-enjoy changed the title feat(IM): markdown message send/reply feat(IM): normalize markdown send/reply output Mar 28, 2026
@91-enjoy 91-enjoy changed the title feat(IM): normalize markdown send/reply output feat: normalize markdown message send/reply output Mar 28, 2026
Change-Id: I71a0cdb8b500ca1496b23fede1f2b2617f16ec63
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Mar 30, 2026

CLA assistant check
All committers have signed the CLA.

@liangshuo-1 liangshuo-1 merged commit 8bd5049 into larksuite:main Mar 30, 2026
4 checks passed
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.

3 participants