fix(ds-bot): settings.trigger 槽位冲突不再让整个插件 failed(M-03)

This commit is contained in:
sansheng 2026-11-10 18:35:03 +08:00
parent c32b2605d5
commit 49cc5ab838
3 changed files with 35 additions and 2 deletions

View File

@ -45,6 +45,28 @@ const rt = ctx.get('dsbot-runtime', false) // 未安装打过补丁的 ds-bot
新装、还没有 Bot 时,侧栏就一个设置入口都没有,用户会以为设置页被删了。
本补丁保留宿主原生设置页;DS Bot 自己的设置仍可在其页面里使用。
## M-03:浏览器端 slots 冲突不再让整个插件「failed」
`client.js`(构建产物)里,`settings.trigger` 的注册没有兜底:
```diff
- slots.inject("settings.trigger", () => slots.register({ name: "settings.trigger" }, TriggerContent))
+ slots.inject("settings.trigger", () => {
+ try {
+ return slots.register({ name: "settings.trigger" }, TriggerContent)
+ } catch (error) {
+ console.warn("[ds-bot] settings.trigger already registered by the host shell; DS Bot trigger skipped", error)
+ return () => {}
+ }
+ })
```
原因:宿主原生设置壳(我们保留的 M-02)已经占用了 `settings.trigger`,ds-bot 再注册会抛
`single slot ... already has a registration at priority 0`;该异常从 `apply` 抛出后,宿主把它记为
`ds-bot: failed`,整个插件(含 Bot 页面)都不加载,随后宿主把 profile 回退成只挂 base + web-app,
表现就是"插件全没了 / 启动崩溃"。`sidebar.settings` 那处上游本来就有 try/catch,不必改。
改的是构建产物,重新构建上游后需重放本补丁。
## 升级步骤
1. 取新版本 npm tarball,解压覆盖本目录(保留本文件与 `NOTICE`)。

View File

@ -22624,7 +22624,15 @@ function installSettingsShell(ctx, { face, actions, ui: ui2, held }) {
};
}
}),
slots.inject("settings.trigger", () => slots.register({ name: "settings.trigger" }, TriggerContent))
slots.inject("settings.trigger", () => {
try {
return slots.register({ name: "settings.trigger" }, TriggerContent);
} catch (error) {
console.warn("[ds-bot] settings.trigger already registered by the host shell; DS Bot trigger skipped", error);
return () => {
};
}
})
];
if (carrier?.protocolVersion === 1) {
disposers.push(slots.inject("sidebar.toggle.badge", () => slots.register({

View File

@ -57,7 +57,10 @@
},
"dsh": {
"client": {
"platform": "web"
"platform": "web",
"inject": [
"@deepseek-ai/dsh-client-ui-primitives"
]
},
"bundle": {
"patch": "./cordis.patch.yml"