Your NameandClaude Sonnet 5
e7cb4edf3a
早前(Part I/K)判断"busy从未在持久化消息里真实出现过，只是本应用自己在 live信令上用的值"，所以没把它并入 CallWebrtcState，只在本地 UI 状态单独 加了个 union。这次拿到手机端真实源码核对，iOS(ServerMessages.swift的7态 枚举)和Android(MsgServerData.java的BUSY)都把busy当成服务端下发的正式 head.webrtc取值之一，和accepted/finished等其余几个是同一级别的东西， 不是本应用凭空发明的——之前的判断依据不足。 补上 case 'busy' 的通话结果文案（"对方忙线中"，和已有的实时来电忙线提示 用词一致），去掉 stores/calls.ts 里两处不再需要的 `| 'busy'` 单独union。 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.