[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"knowledge-\u002Fapi\u002Fknowledge\u002Fteam-documents\u002F06":3,"knowledge-related-\u002Fknowledge\u002Fteam-documents\u002F06":582,"knowledge-series-\u002Fknowledge\u002Fteam-documents\u002F06":609},{"source":4,"connector":5,"page":6},"sqlite","better-sqlite3",{"path":7,"title":8,"description":9,"category":10,"tags":11,"date":16,"pinned":17,"draft":17,"body":18,"seo":578,"stem":579,"id":580,"extension":581},"\u002Fknowledge\u002Fteam-documents\u002F06","企业微信与小程序工单问题","企微师傅端与商家小程序端长期共用一套代码，页面与组件嵌套边界不清晰、引入规范缺失、公共代码与端侧代码耦合度高，导致维护成本持续上升。本文给出拆分为两套独立项目的架构建议，并说明边界划分、迁移注意事项与性能优化方向。","团队文档",[12,13,14,15],"team","mobile","wecom","performance","2025-10-01",false,{"type":19,"value":20,"toc":563},"minimark",[21,24,28,41,44,47,123,127,130,225,228,254,257,292,295,298,308,315,318,350,353,373,376,379,455,458,489,492,542,545,548,551],[22,23,8],"h1",{"id":8},[25,26,27],"h2",{"id":27},"背景",[29,30,31,32,36,37,40],"p",{},"工单相关业务同时服务两类使用者：",[33,34,35],"strong",{},"企业微信师傅端","（内部\u002F外部人员在企业微信内处理工单）与",[33,38,39],{},"小程序商家端","（商家在微信小程序内查看、跟进工单）。历史实现为节省初期开发成本，长期采用「一套代码、按运行环境做条件分支」的方式承载两端页面，随着工单流程不断迭代，该方式的维护成本逐渐显现。",[29,42,43],{},"早期这种“一套代码走两端”的选择并非没有理由：初期功能简单、两端差异小，共用代码确实能节省一部分重复开发时间。但随着工单流程新增「二次上门」「多级审批」「小程序订阅消息提醒」等两端专属能力，条件分支数量呈增长趋势，公共模块中夹杂端侧判断的比例也随之上升，团队在规划下一阶段迭代时，需要重新评估这套代码结构是否还能支撑后续需求。",[25,45,46],{"id":46},"主要痛点",[48,49,50,66],"table",{},[51,52,53],"thead",{},[54,55,56,60,63],"tr",{},[57,58,59],"th",{},"痛点",[57,61,62],{},"具体表现",[57,64,65],{},"影响",[67,68,69,81,92,112],"tbody",{},[54,70,71,75,78],{},[72,73,74],"td",{},"页面\u002F组件边界不清晰",[72,76,77],{},"企微师傅端与商家端页面、组件互相嵌套引用，同一组件内部混杂两端分支逻辑",[72,79,80],{},"改一端逻辑容易误改到另一端；代码审查成本高",[54,82,83,86,89],{},[72,84,85],{},"引入规范缺失",[72,87,88],{},"组件模块引入方式不统一（相对路径、别名、按端条件引入并存）",[72,90,91],{},"新人上手成本高，容易引入循环依赖或重复打包",[54,93,94,97,109],{},[72,95,96],{},"公共代码与端侧代码耦合",[72,98,99,100,104,105,108],{},"工具函数、状态管理、路由守卫中夹杂端侧判断（如 ",[101,102,103],"code",{},"isWecom","、",[101,106,107],{},"isMiniProgram","）",[72,110,111],{},"修改公共逻辑需要同时验证两端，回归成本高",[54,113,114,117,120],{},[72,115,116],{},"加载性能一般",[72,118,119],{},"两端能力打包在同一产物中，实际只需要其中一端的代码也会被下载",[72,121,122],{},"首屏体积偏大，弱网环境下体验下降",[25,124,126],{"id":125},"为何建议拆分为两套代码-两个项目","为何建议拆分为两套代码 \u002F 两个项目",[29,128,129],{},"企业微信与小程序在运行环境、组件体系、鉴权与跳转方式上存在本质差异，勉强用一套代码覆盖两端，长期看维护收益低于拆分成本。",[48,131,132,143],{},[51,133,134],{},[54,135,136,139,141],{},[57,137,138],{},"对比项",[57,140,35],{},[57,142,39],{},[67,144,145,156,167,182,203,214],{},[54,146,147,150,153],{},[72,148,149],{},"运行容器",[72,151,152],{},"企业微信内嵌 H5 \u002F 企微 JS-SDK",[72,154,155],{},"微信小程序原生运行时",[54,157,158,161,164],{},[72,159,160],{},"组件体系",[72,162,163],{},"Web 组件库（如 Vant \u002F Element 等）",[72,165,166],{},"小程序原生组件 + 小程序组件库",[54,168,169,172,175],{},[72,170,171],{},"鉴权方式",[72,173,174],{},"企业微信免登 + 内部账号体系",[72,176,177,178,181],{},"小程序 ",[101,179,180],{},"login"," 态 + 商家账号体系",[54,183,184,187,197],{},[72,185,186],{},"跳转能力",[72,188,189,192,193,196],{},[101,190,191],{},"location.href"," \u002F 企微 JS-SDK 跳转、",[101,194,195],{},"wx.agentConfig"," 相关能力",[72,198,199,202],{},[101,200,201],{},"wx.navigateTo"," \u002F 小程序路由栈",[54,204,205,208,211],{},[72,206,207],{},"主题与设计规范",[72,209,210],{},"偏内部工具风格",[72,212,213],{},"偏商家 C 端体验风格",[54,215,216,219,222],{},[72,217,218],{},"能力依赖",[72,220,221],{},"企业微信会话、消息、审批等强相关 API",[72,223,224],{},"小程序支付、分享、订阅消息等 API",[29,226,227],{},"若强行合并为一套代码，通常会出现以下问题：",[229,230,231,238,248],"ul",{},[232,233,234,237],"li",{},[33,235,236],{},"能力不可迁移","：企微端无法直接调用小程序专属能力（如小程序支付、订阅消息），小程序端也无法使用企微专属能力（会话存档、企微消息卡片等），条件分支只能越堆越多；",[232,239,240,243,244,247],{},[33,241,242],{},"鉴权链路冲突","：小程序页面依赖独立登录态与 ",[101,245,246],{},"session_key"," 体系，企微页面依赖企业身份免登，二者混在一套路由与状态管理中，容易出现登录态互相污染或刷新后态丢失；",[232,249,250,253],{},[33,251,252],{},"构建与发布耦合","：任一端发版都需要重新构建、验证整个产物，无法独立发布节奏。",[25,255,256],{"id":256},"边界划分建议",[258,259,260,266,272,281],"ol",{},[232,261,262,265],{},[33,263,264],{},"按运行环境彻底拆分为两个独立项目\u002F仓库","，各自维护构建配置、依赖版本与发布节奏；",[232,267,268,271],{},[33,269,270],{},"企业微信端","优先使用企业微信原生能力与组件体系，涉及「二次上门」「工单会话」「审批流」等场景直接对接企微 JS-SDK，不做小程序兼容层；",[232,273,274,277,278,280],{},[33,275,276],{},"小程序端","优先使用小程序原生组件与能力（如 ",[101,279,201],{},"、订阅消息、原生支付），不引入企微专属依赖；",[232,282,283,284,287,288,291],{},"若确有",[33,285,286],{},"业务口径一致","的部分（如工单状态枚举、金额计算规则、文案），可下沉为",[33,289,290],{},"纯逻辑的公共包","（不含 UI、不含端侧判断），通过 npm 私有包或 monorepo 子包方式复用，避免把 UI 层也强行合并。",[25,293,294],{"id":294},"拆分后目录结构建议",[29,296,297],{},"两个仓库各自维护独立的目录结构，公共逻辑包以子包或私有 npm 包形式被两端引用：",[299,300,306],"pre",{"className":301,"code":303,"language":304,"meta":305},[302],"language-text","wecom-worker\u002F            # 企业微信师傅端仓库\n  src\u002F\n    pages\u002F\n    components\u002F\n    sdk\u002F                 # 企微 JS-SDK 封装\n  vite.config.ts\n\nmerchant-miniapp\u002F        # 小程序商家端仓库\n  src\u002F\n    pages\u002F\n    components\u002F\n  project.config.json\n\n@org\u002Fwork-order-shared\u002F  # 纯逻辑公共包（工单状态枚举、金额计算等）\n  src\u002F\n    enums.ts\n    calc.ts\n  package.json\n","text","",[101,307,303],{"__ignoreMap":305},[29,309,310,311,314],{},"公共包只做纯逻辑导出，不引入任何 UI 组件或端侧 SDK，两端各自按需 ",[101,312,313],{},"import"," 后在本端 UI 中使用。",[25,316,317],{"id":317},"迁移注意事项",[229,319,320,326,332,338,344],{},[232,321,322,325],{},[33,323,324],{},"接口层面","：确认后端接口是否已按「渠道来源」区分返回字段（如工单来源标记企微\u002F小程序），迁移过程中避免两端同时读写导致状态覆盖；",[232,327,328,331],{},[33,329,330],{},"鉴权迁移","：企微免登与小程序登录分别独立改造，迁移期建议保留双写日志，便于定位登录态错乱问题；",[232,333,334,337],{},[33,335,336],{},"灰度节奏","：建议先拆分低风险的展示型页面（列表、详情），再迁移涉及下单\u002F审批等高风险交互页面，降低整体风险；",[232,339,340,343],{},[33,341,342],{},"历史链接兼容","：企业微信历史消息卡片、小程序历史分享路径中可能固化了旧路由，拆分后需保留一段时间的路由重定向；",[232,345,346,349],{},[33,347,348],{},"组件库对齐","：拆分后两端设计规范可能出现差异，建议提前与产品\u002F设计确认，避免用户感知到「同一功能两套体验」的割裂感。",[25,351,352],{"id":352},"性能优化建议",[229,354,355,358,367,370],{},[232,356,357],{},"拆分后各端产物只包含自身依赖，天然减少无关代码的下载与解析；",[232,359,360,361,366],{},"企微端可结合 ",[362,363,365],"a",{"href":364},"\u002Fknowledge\u002Fteam-documents\u002F07","企业微信群工具打开缓慢原因分析"," 中的构建体积、资源预加载、SDK 初始化链路优化经验，缩短首次进入耗时；",[232,368,369],{},"小程序端建议关注分包加载、按需注入组件，避免主包体积超限；",[232,371,372],{},"公共逻辑包应保持轻量、无副作用，避免因公共包体积增长间接拖慢两端首屏。",[25,374,375],{"id":375},"实施排期建议",[29,377,378],{},"拆分不建议“一刀切”式停机重构，按风险从低到高分阶段推进：",[48,380,381,397],{},[51,382,383],{},[54,384,385,388,391,394],{},[57,386,387],{},"阶段",[57,389,390],{},"内容",[57,392,393],{},"周期参考",[57,395,396],{},"风险",[67,398,399,413,427,441],{},[54,400,401,404,407,410],{},[72,402,403],{},"第一阶段",[72,405,406],{},"新建两个独立仓库，搭建各自构建配置与基础依赖，公共逻辑包先以最小集合（枚举、金额计算）落地",[72,408,409],{},"1-2 周",[72,411,412],{},"低，不影响存量线上功能",[54,414,415,418,421,424],{},[72,416,417],{},"第二阶段",[72,419,420],{},"迁移展示型页面（列表、详情），两端并行验证",[72,422,423],{},"2-3 周",[72,425,426],{},"低-中，回退成本低",[54,428,429,432,435,438],{},[72,430,431],{},"第三阶段",[72,433,434],{},"迁移交互型页面（下单、审批、状态变更）",[72,436,437],{},"2-4 周",[72,439,440],{},"中-高，需重点验证鉴权与状态一致性",[54,442,443,446,449,452],{},[72,444,445],{},"第四阶段",[72,447,448],{},"下线旧路由与旧代码，清理条件分支",[72,450,451],{},"1 周",[72,453,454],{},"低，但需确认历史链接兼容期已过",[25,456,457],{"id":457},"常见疑问",[258,459,460,469,481],{},[232,461,462,465,468],{},[33,463,464],{},"两套代码会不会增加维护成本？",[466,467],"br",{},"\n短期看确实需要维护两个仓库，但长期看两端条件分支消失后，单侧改动不再需要担心「误改另一端」，整体回归成本反而下降。",[232,470,471,474,476,477,480],{},[33,472,473],{},"公共逻辑包要不要包含请求层？",[466,475],{},"\n不建议。企微端与小程序端的网络请求封装（尤其是鉴权头、",[101,478,479],{},"baseURL","、错误处理）差异较大，强行合并容易引入隐藏的端侧判断，违背拆分初衷；公共包应只保留纯函数逻辑。",[232,482,483,486,488],{},[33,484,485],{},"拆分后两端设计不一致怎么办？",[466,487],{},"\n属于预期内的短期现象，建议提前与产品\u002F设计同步拆分计划，必要时给出统一的视觉规范作为两端后续迭代的共同基线，而不是强行在代码层维持一致。",[25,490,491],{"id":491},"回归检查清单",[229,493,496,506,512,518,524,530,536],{"className":494},[495],"contains-task-list",[232,497,500,505],{"className":498},[499],"task-list-item",[501,502],"input",{"disabled":503,"type":504},true,"checkbox"," 企业微信端所有工单相关页面（列表、详情、审批）在拆分后可正常访问，无残留小程序端专属依赖报错；",[232,507,509,511],{"className":508},[499],[501,510],{"disabled":503,"type":504}," 小程序端所有工单相关页面在拆分后可正常访问，无残留企微 JS-SDK 相关报错；",[232,513,515,517],{"className":514},[499],[501,516],{"disabled":503,"type":504}," 公共逻辑包（状态枚举、金额计算规则）在两端引用后计算结果一致，重点覆盖边界值（如金额为 0、状态为空）；",[232,519,521,523],{"className":520},[499],[501,522],{"disabled":503,"type":504}," 企业微信历史消息卡片与小程序历史分享路径可正确重定向到新页面，不出现 404 或白屏；",[232,525,527,529],{"className":526},[499],[501,528],{"disabled":503,"type":504}," 两端鉴权链路（企微免登 \u002F 小程序登录态）互不影响，切换账号或重新登录后状态不串号；",[232,531,533,535],{"className":532},[499],[501,534],{"disabled":503,"type":504}," 两端各自的构建产物体积较拆分前下降，且不包含另一端专属依赖（可通过构建分析工具核实）；",[232,537,539,541],{"className":538},[499],[501,540],{"disabled":503,"type":504}," 灰度期间新老入口并存时，同一工单在两个入口查看的数据一致，无因渠道字段处理不一致导致的展示差异。",[25,543,544],{"id":544},"总结",[29,546,547],{},"企微师傅端与小程序商家端在运行环境、组件体系、鉴权链路上差异明显，是否拆分不应仅从“短期是否好维护”判断，而应从长期迭代成本与两端独立发布能力综合评估。建议尽快完成边界拆分，公共逻辑通过纯逻辑包复用，两端 UI 与端侧能力各自独立演进。",[25,549,550],{"id":550},"相关链接",[229,552,553,557],{},[232,554,555],{},[362,556,365],{"href":364},[232,558,559],{},[362,560,562],{"href":561},"\u002Fknowledge\u002Fteam-documents\u002F17","支付中转页面升级实践",{"title":305,"searchDepth":564,"depth":564,"links":565},2,[566,567,568,569,570,571,572,573,574,575,576,577],{"id":27,"depth":564,"text":27},{"id":46,"depth":564,"text":46},{"id":125,"depth":564,"text":126},{"id":256,"depth":564,"text":256},{"id":294,"depth":564,"text":294},{"id":317,"depth":564,"text":317},{"id":352,"depth":564,"text":352},{"id":375,"depth":564,"text":375},{"id":457,"depth":564,"text":457},{"id":491,"depth":564,"text":491},{"id":544,"depth":564,"text":544},{"id":550,"depth":564,"text":550},{"title":8,"description":9},"knowledge\u002Fteam-documents\u002F06","knowledge\u002Fknowledge\u002Fteam-documents\u002F06.md","md",{"items":583},[584,589,592,597,601,605],{"path":585,"title":586,"description":587,"category":10,"score":588},"\u002Fknowledge\u002Fteam-documents\u002F22","企业微信 uni-app H5：OAuth 回退白屏与列表缓存","第三方 BI 报表项目，企业微信内嵌 H5，uni-app 编译，history 模式。主页面 BiLink 同时承担静默授权和列表展示，上线后碰到两个问题：授权完清掉 URL 参数，iOS 侧滑返回还是白屏；列表加了缓存以后，刷新行…",15,{"path":364,"title":365,"description":590,"category":10,"score":591},"企业微信群工具首次打开耗时明显偏长，通过构建体积、静态资源阻塞、路由鉴权链路、SDK 初始化四个方向逐层排查，定位主要耗时集中在 wx.agentConfig 初始化，并给出排查步骤与优化建议。",12,{"path":593,"title":594,"description":595,"category":10,"score":596},"\u002Fknowledge\u002Fteam-documents\u002F19","GridView 宫格加载渲染优化","系统首页 GridView 宫格模块接口耗时不高，但首次进入总耗时接近 22s。复盘耗时分层定位过程、代码层面的瓶颈（约 2000 行、100 个 tab 重复节点）、优化手段与最终指标对比。",9,{"path":598,"title":599,"description":600,"category":10,"score":596},"\u002Fknowledge\u002Fteam-documents\u002F12","系统自动更新说明","对比商家系统与 BOSS 系统在发版后的更新体验差异，说明两者共用的离线缓存\u002FPWA 插件的自动更新与手动提示更新两种模式，并结合知识库《网站更新（一）（二）》给出统一策略建议。",{"path":602,"title":603,"description":604,"category":10,"score":596},"\u002Fknowledge\u002Fteam-documents\u002F13","新商家系统性能优化实践","商家系统新版本上线后，团队持续针对构建效率与用户体验做了一轮系统性优化。本文记录核心方案与落地结果，供后续版本复用。",{"path":606,"title":607,"description":608,"category":10,"score":596},"\u002Fknowledge\u002Fteam-documents\u002F04","老系统升级与兼容改造实践","公司原有业务系统采用 Node + jQuery 架构，长期运行后暴露出典型遗留系统问题：",{"series":610,"title":611,"items":612,"index":684,"prev":685,"next":686},"team-documents","team documents",[613,617,621,625,627,631,632,634,638,642,646,650,652,654,658,662,666,668,672,674,678,682],{"path":614,"title":615,"date":616,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F01","执行价格弹窗：表头 \u002F 表体合并与可配置表格","2024-07-27",{"path":618,"title":619,"date":620,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F02","防篡改水印","2024-01-09",{"path":622,"title":623,"date":624,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F03","键盘弹起导致底部被顶起问题（H5 适配）","2024-09-17",{"path":606,"title":607,"date":626,"pinned":17},"2024-12-12",{"path":628,"title":629,"date":630,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F05","内部插件 \u002F 工具库开发实践","2021-08-19",{"path":7,"title":8,"date":16,"pinned":17},{"path":364,"title":365,"date":633,"pinned":17},"2020-04-12",{"path":635,"title":636,"date":637,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F08","属性排序需求","2024-06-16",{"path":639,"title":640,"date":641,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F09","同业主重复单提醒规则","2020-06-07",{"path":643,"title":644,"date":645,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F10","图片上传前的自定义水印实践","2021-06-10",{"path":647,"title":648,"date":649,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F11","系统下单（重复单提示框）异常复盘","2023-11-21",{"path":598,"title":599,"date":651,"pinned":17},"2025-05-26",{"path":602,"title":603,"date":653,"pinned":17},"2025-04-08",{"path":655,"title":656,"date":657,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F14","选项卡切换与 Loading 状态封装","2019-11-03",{"path":659,"title":660,"date":661,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F15","移动端返回事件触发两次问题复盘","2021-03-09",{"path":663,"title":664,"date":665,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F16","在线协作表格接入实践","2023-10-27",{"path":561,"title":562,"date":667,"pinned":17},"2022-10-15",{"path":669,"title":670,"date":671,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F18","中英文输入法下搜索触发冲突复盘","2024-09-01",{"path":593,"title":594,"date":673,"pinned":17},"2026-03-17",{"path":675,"title":676,"date":677,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F20","H5 GPS 定位问题说明","2023-08-31",{"path":679,"title":680,"date":681,"pinned":17},"\u002Fknowledge\u002Fteam-documents\u002F21","vxe-table 行 Hover 联动高亮","2024-08-31",{"path":585,"title":586,"date":683,"pinned":17},"2023-08-17",5,{"path":628,"title":629,"date":630,"pinned":17},{"path":364,"title":365,"date":633,"pinned":17}]