Your Name
823a47e182
群公告发布后自动生成的通知消息，真实content是{text:"群公告\n<内容>"}这种
扁平对象（不是纯字符串，也不是标准Drafty的{txt,fmt,ent}结构），且
head['x-im-type']是"text"而不是已处理的"system_notice"，落到Drafty处理
分支后既渲染不出气泡正文、列表预览也变成字面的"undefined"字符串。
抽出dispatch.ts里原本只服务system_notice的{text}扁平内容识别逻辑
（重命名为flatTextContentOf并导出），在renderDrafty和
formatMessagePreview的Drafty分支之前都接上——不改变已有的居中系统提示
样式（这条消息本来就该是普通气泡，发送者信息一直是正确的，只是正文
丢了），只是把"文本内容是扁平{text}对象"这一种情况也当作合法纯文本处理。
实测：真实发布一条群公告后，气泡正文和列表预览都正确显示"群公告
全功能测试公告内容"，不再是空白或"undefined"。
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.