Repository navigation
feat: 跟随 DSH 0.2.2-rc.1 —— 导航图标改用官方 settings.section.icon(0.5.1) - #13
Merged
Merged
Conversation
…host dependency
DSH 0.2.2-rc.1 added the official settings.section.icon slot (list / inline /
root, declared by dsh-client-ui-settings-general, rendered with {size, active}
and {only: row.id}). The plugin had carried a DOM workaround for exactly this
gap - row marking plus a CSS mask - with a note that it must be deleted once
the slot exists. This removes it and registers the glyph the native way.
- nav icon: slots.inject('settings.section.icon') with id 'token-stats'
(the contract matches on the section id; a mismatch renders nothing, no error)
- delete installSettingsNavIcon / NAV_ICON_MASK / NAV_ICON_CSS; older kernels
simply fall back to the official gear
- cordis peer+dev ~4.0.5 -> ~4.1.0; schemastery ~3.18.5 -> ~3.19.0 (host parity)
- dsh.client.inject += @deepseek-ai/dsh-client-ui-settings-general
- dsh.verifiedAgainst 0.2.1-rc.4 -> 0.2.2-rc.1; engines.dsh unchanged
(0.2.2-rc.1 satisfies >=0.2.1-rc.3 <0.3.0 under includePrerelease)
- tests 234 -> 238 (tests/client-settings-icon.test.js)
- CHANGELOG: fold these items into the pending 0.5.1 section and restore
descending order (0.4.0 sat above 0.5.0)
xinspark
force-pushed
the
release/0.5.1
branch
from
November 4, 2026 23:30
3e7ecee to
9bcec51
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
0.5.1:跟随 DSH 0.2.2-rc.1
为什么
本地 DSH 从
0.2.1-rc.4升到0.2.2-rc.1。核对结论:engines.dsh不用改:0.2.2-rc.1仍落在>=0.2.1-rc.3 <0.3.0内 —— DSH 的evaluatePluginCompatibility用semver.satisfies(..., { includePrerelease: true })判定(
dsh-app-boot/lib/index.js:1094-1096),预发布版参与区间匹配。list()/read(offset, length, options)签名不变;tokenUsage投影字段不变(只有contextPressure多了summary: false);settings.section/conversation.composer.dock槽位契约不变。verify:typert(4 端点)、verify:remote(7/7)。改了什么
1. 导航图标改走官方槽位(净删约 50 行)
0.2.2-rc.1 新增
settings.section.icon(list / inline / root,契约在@deepseek-ai/dsh-client-ui-settings-general):nav rows 用renderSlot("settings.section.icon", { size, active }, { only: row.id })渲染,注册 id 必须等于 section id,对不上就永不渲染、也不报错。
这正是 0.2.1 时代那段 DOM 补缺注释里写的「官方一旦补上就整体删除」——现在删掉:
属性标记 + CSS mask + MutationObserver 全部移除,换成一次
slots.register。旧内核没有这个槽时 inject 不触发,行内图标退化成官方齿轮,其余不变。
2. 依赖基线跟进
peerDependencies["@deepseek-ai/cordis"]~4.0.5~4.1.0devDependencies["@deepseek-ai/cordis"]~4.0.5~4.1.0dependencies["@deepseek-ai/schemastery"]~3.18.5~3.19.0dsh.verifiedAgainst0.2.1-rc.40.2.2-rc.1dsh.client.inject@deepseek-ai/dsh-client-ui-settings-general验证
npm test:228 / 228。新增tests/client-settings-icon.test.js(4 条:注册 id 必须等于section id、旧 DOM 补缺必须删净、图标按
size渲染且只用currentColor、dsh.client.inject必须声明槽位归属模块)。
npm run verify:typert:OK(4 端点,namespacedsh-plugin-usage)npm run verify:remote:7/7dsh-session、dsh-session-persistence-jsonl、dsh-session-projection、dsh-token-meter、dsh-client-ui-conversation、dsh-client-ui-settings、dsh-typert-registry:本插件依赖的签名均未变。发布
tag 与
npm publish留到合并之后(本机 npm 登录态已失效,需先npm login --registry=https://registry.npmjs.org/)。