Your NameandClaude Sonnet 5
eb0a6eba7e
真实数据库排查确认根因：forwardMessage()原来无条件把 msg.content 喂给
Drafty.forwardedContent(toDraftyContent(...))，假设内容永远是纯字符串或真
Drafty文档({txt,fmt,ent})。但手机端把文本/图片/语音/视频/名片都发成扁平非
Drafty JSON(如 {"text":"11"})，只靠 head['x-im-type']/head.webrtc 标记类型
——对这类对象跑 Drafty 处理会退化成空内容，SDK 出站的 simplify() 又会把空
content 整个从包里剥掉，服务端收到的 {pub} 根本没有 content 字段，落库后
content/content_nonce 都是真正的 NULL，客户端据此正确地（从自己的角度）把
它当成"已撤回"渲染成"⚠ 消息已删除"。
用 SSH+kubectl exec 直接查了k3s上的真实MySQL(meeting_im库, im_003_group_
messages_202609/im_003_messages两张表)，确认了具体是哪几条消息、它们的
head/content 真实长什么样，而不是猜测。
修复：flatForwardPayload() 识别这几种扁平内容形状，文本类重建成真正的
Drafty文本，附件/名片/通话结果类原样保留内容和 x-im-type/webrtc 标记（接收
端已有的对应dispatch逻辑本来就认识这些形状），只有真正的纯字符串/Drafty
内容才继续走原来的 Drafty.forwardedContent() 路径。
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Oxc
- @vitejs/plugin-react-swc uses SWC
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the Oxlint configuration
If you are developing a production application, we recommend enabling type-aware lint rules by installing oxlint-tsgolint and editing .oxlintrc.json:
{
"$schema": "./node_modules/oxlint/configuration_schema.json",
"plugins": ["react", "typescript", "oxc"],
"options": {
"typeAware": true
},
"rules": {
"react/rules-of-hooks": "error",
"react/only-export-components": ["warn", { "allowConstantExport": true }]
}
}
See the Oxlint rules documentation for the full list of rules and categories.