6 Commits

Include renames

Author	SHA1	Message	Date
Your Name	df173879fa	fix: route IM clients through current origin	2026-10-19 17:23:34 +08:00
richjohnrambo	c30c5c07c7	feat(web): add tenant user registration flow	2026-10-17 00:48:08 +08:00
Austin	a8d3504424	feat: 实现跨端引用回复协议，新增 QuoteBar 组件支持消息引用 ... 本次提交实现了与 iOS 对齐的跨端消息引用协议，新增 QuoteBar 组件用于渲染引用消息栏，重构发送逻辑支持文本和媒体消息的引用功能。主要改动包括： - 新增 reply.ts 处理引用数据的构建和解析 - 新增 QuoteBar 组件渲染引用消息预览 - 重构发送逻辑，将引用快照放入消息头部而非内容 - 调整代理配置指向本地开发环境 - 优化消息操作权限，支持名片和媒体消息引用	2026-09-23 20:40:47 +08:00
Your NameandClaude Sonnet 5	e78437cb2a	fix(web): upgrade http OSS URLs to https to fix mixed-content block ... Aliyun OSS sometimes returns presigned URLs as http:// even though every page here is served over https:// -- the browser silently blocks these as mixed content, which is why images (e.g. avatar) failed to display after upload. Added upgradeToHttps() and wired it into fileDownloadUrl() (the single chokepoint every image/attachment fetch in the app resolves through) plus the three chat-attachment send paths, so both freshly fetched and newly-persisted URLs get the scheme fix. Also fixed ProfileSettingsPage's avatar upload handler, which extracted the file id by parsing the upload response's `url` with .split('/').pop() instead of just reading the `file_id` field the response already provides -- fragile against exactly this kind of full-URL response and the most likely actual trigger for the reported bug. vite.config.ts: dev server port now respects $PORT if set, falls back to 8094 -- unrelated cleanup, needed it to run a second local dev server for verification alongside another concurrent session's. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-16 00:18:31 +08:00
Your NameandClaude Sonnet 5	8cdd84152d	企业码解析+登录跑通真实后端：Tinode连接适配层、类型化API客户端、会话store ... lib/tinode/connection.ts：单例Tinode连接+自己的发布订阅层——SDK的onConnect/onDisconnect/onLogin 是单槽位属性（赋值会互相覆盖），不是真正的多监听器事件源，所以这里统一接管这几个槽位，自己 扇出给任意数量的React订阅方（lib/tinode/hooks.ts的useSyncExternalStore）。installTenantHiPatch 照搬旧应用tinode-web.jsx的实现搬过来——服务端{hi}包的tenant字段SDK本身没有API，只能在原始 sendText层面注入，这是后端协议的真实约束，不是旧代码库特有的写法。 lib/api/client.ts：REST客户端按旧应用src/lib/im-api.js的request函数+完整REASON_MESSAGES错误码 翻译表搬过来（含请求头X-MeetingIM-APIKey等几个月联调换来的正确写法），这次是重新用TypeScript 写、不是复制文件，但端点行为对齐。 实机联调过程中发现并修正了一处凭记忆猜错的地方：tenants/resolve真实响应结构是 {endpoints:{api,file,websocket}, tenant:{code,name}}，不是我最初假设的顶层{code,name}—— 已用真实请求验证修正。用企业码default解析成功（显示"Default Tenant"）+ 一次真实错误密码 登录尝试（服务端真实401，错误提示正确显示"账号或密码错误"）两步都对着真实后端验证通过， 不是只测了正确路径。 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-08 00:38:50 +08:00
Your NameandClaude Sonnet 5	8bcd9f3a5b	新分支：Vite+React19+TS+Tailwind v4 重新搭建，先跑通四级响应式布局壳 ... 不再沿用旧 im_webapp 的技术栈（webpack + class组件 + 15000行全局CSS + 手搓History路由）， 按业务重新选型：Vite/React Router/Zustand预留/TanStack Query/保留tinode-sdk真实依赖 （协议客户端本身没有重写的业务理由）。新代码放在 web/ 子目录，旧代码原样保留在仓库根目录， 两者共存到重写完成。 这一步先验证布局壳本身：NavRail（消息/通讯录/收藏/文件助手/通话记录/设置）+ 会话列表 + 主区域 + 详情栏，按设计稿的四档断点（<640/640-959/960-1279/≥1280）用真实浏览器宽度逐档验证 过——两列及以下"列表/主区域二选一+返回键"、三列"详情栏抽屉化"、四列"详情栏常驻"均已用 真实点击/返回验证正确，不是只看了截图。会话列表和聊天内容目前是占位数据，业务数据接入和 Tinode连接是下一步。 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-08 00:24:11 +08:00