dsh-group-status 0.3.0 → 0.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +69 -0
- package/README.en.md +12 -10
- package/README.md +14 -10
- package/lib/client.js +1294 -281
- package/lib/client.js.map +1 -1
- package/lib/index.js +7 -4
- package/lib/types/client/BadgeSettingsCard.d.ts.map +1 -1
- package/lib/types/client/BadgeSettingsCard.js +6 -6
- package/lib/types/client/BadgeSettingsCard.js.map +1 -1
- package/lib/types/client/badge-field.d.ts +33 -10
- package/lib/types/client/badge-field.d.ts.map +1 -1
- package/lib/types/client/badge-field.js +35 -16
- package/lib/types/client/badge-field.js.map +1 -1
- package/lib/types/client/badge-labels.d.ts +3 -3
- package/lib/types/client/badge-labels.js +3 -3
- package/lib/types/client/badge-settings.d.ts +0 -25
- package/lib/types/client/badge-settings.d.ts.map +1 -1
- package/lib/types/client/badge-settings.js +0 -18
- package/lib/types/client/badge-settings.js.map +1 -1
- package/lib/types/client/contract/slots.d.ts +39 -21
- package/lib/types/client/contract/slots.d.ts.map +1 -1
- package/lib/types/client/contract/slots.js.map +1 -1
- package/lib/types/client/contract/toast.d.ts +67 -0
- package/lib/types/client/contract/toast.d.ts.map +1 -0
- package/lib/types/client/contract/toast.js +2 -0
- package/lib/types/client/contract/toast.js.map +1 -0
- package/lib/types/client/facets.d.ts +39 -5
- package/lib/types/client/facets.d.ts.map +1 -1
- package/lib/types/client/facets.js +48 -4
- package/lib/types/client/facets.js.map +1 -1
- package/lib/types/client/index.d.ts +6 -3
- package/lib/types/client/index.d.ts.map +1 -1
- package/lib/types/client/index.js +48 -13
- package/lib/types/client/index.js.map +1 -1
- package/lib/types/client/locales.d.ts +14 -8
- package/lib/types/client/locales.d.ts.map +1 -1
- package/lib/types/client/locales.js +14 -8
- package/lib/types/client/locales.js.map +1 -1
- package/lib/types/client/navigation.d.ts +45 -12
- package/lib/types/client/navigation.d.ts.map +1 -1
- package/lib/types/client/navigation.js +102 -26
- package/lib/types/client/navigation.js.map +1 -1
- package/lib/types/client/rows/GroupBadge.d.ts +4 -4
- package/lib/types/client/rows/GroupBadge.d.ts.map +1 -1
- package/lib/types/client/rows/GroupBadge.js +10 -7
- package/lib/types/client/rows/GroupBadge.js.map +1 -1
- package/lib/types/client/rows/Rows.d.ts.map +1 -1
- package/lib/types/client/rows/Rows.js +4 -4
- package/lib/types/client/rows/Rows.js.map +1 -1
- package/lib/types/client/rows/WorkspaceBrowser.d.ts +1 -1
- package/lib/types/client/rows/WorkspaceBrowser.d.ts.map +1 -1
- package/lib/types/client/rows/WorkspaceBrowser.js +66 -61
- package/lib/types/client/rows/WorkspaceBrowser.js.map +1 -1
- package/lib/types/client/session-actions/ArchiveSession.js +1 -1
- package/lib/types/client/session-actions/ArchiveSession.js.map +1 -1
- package/lib/types/client/session-actions/ForkSession.d.ts +5 -4
- package/lib/types/client/session-actions/ForkSession.d.ts.map +1 -1
- package/lib/types/client/session-actions/ForkSession.js +7 -4
- package/lib/types/client/session-actions/ForkSession.js.map +1 -1
- package/lib/types/client/session-actions/PinSession.js +1 -1
- package/lib/types/client/session-actions/PinSession.js.map +1 -1
- package/lib/types/client/session-actions/RowActionToast.d.ts +5 -8
- package/lib/types/client/session-actions/RowActionToast.d.ts.map +1 -1
- package/lib/types/client/session-actions/RowActionToast.js +10 -49
- package/lib/types/client/session-actions/RowActionToast.js.map +1 -1
- package/lib/types/client/session-actions/SessionId.d.ts +8 -0
- package/lib/types/client/session-actions/SessionId.d.ts.map +1 -0
- package/lib/types/client/session-actions/SessionId.js +16 -0
- package/lib/types/client/session-actions/SessionId.js.map +1 -0
- package/lib/types/client/session-watermarks.d.ts +30 -0
- package/lib/types/client/session-watermarks.d.ts.map +1 -0
- package/lib/types/client/session-watermarks.js +54 -0
- package/lib/types/client/session-watermarks.js.map +1 -0
- package/lib/types/client/shortcuts.d.ts +2 -7
- package/lib/types/client/shortcuts.d.ts.map +1 -1
- package/lib/types/client/shortcuts.js +7 -11
- package/lib/types/client/shortcuts.js.map +1 -1
- package/lib/types/client/toast/Toast.d.ts +41 -0
- package/lib/types/client/toast/Toast.d.ts.map +1 -0
- package/lib/types/client/toast/Toast.js +44 -0
- package/lib/types/client/toast/Toast.js.map +1 -0
- package/lib/types/client/toast/register.d.ts +11 -0
- package/lib/types/client/toast/register.d.ts.map +1 -0
- package/lib/types/client/toast/register.js +162 -0
- package/lib/types/client/toast/register.js.map +1 -0
- package/lib/types/client/tree.d.ts +16 -1
- package/lib/types/client/tree.d.ts.map +1 -1
- package/lib/types/client/tree.js +20 -8
- package/lib/types/client/tree.js.map +1 -1
- package/lib/types/client/use-registered-facets.d.ts +11 -0
- package/lib/types/client/use-registered-facets.d.ts.map +1 -0
- package/lib/types/client/use-registered-facets.js +48 -0
- package/lib/types/client/use-registered-facets.js.map +1 -0
- package/lib/types/host-contract.d.ts +57 -0
- package/lib/types/host-contract.d.ts.map +1 -0
- package/lib/types/host-contract.js +84 -0
- package/lib/types/host-contract.js.map +1 -0
- package/lib/types/index.d.ts +7 -10
- package/lib/types/index.d.ts.map +1 -1
- package/lib/types/index.js +7 -4
- package/lib/types/index.js.map +1 -1
- package/package.json +34 -30
- package/lib/types/client/facet-visibility.d.ts +0 -17
- package/lib/types/client/facet-visibility.d.ts.map +0 -1
- package/lib/types/client/facet-visibility.js +0 -18
- package/lib/types/client/facet-visibility.js.map +0 -1
- package/lib/types/client/legacy/bridge.d.ts +0 -30
- package/lib/types/client/legacy/bridge.d.ts.map +0 -1
- package/lib/types/client/legacy/bridge.js +0 -58
- package/lib/types/client/legacy/bridge.js.map +0 -1
- package/lib/types/client/legacy/register-legacy-facets.d.ts +0 -14
- package/lib/types/client/legacy/register-legacy-facets.d.ts.map +0 -1
- package/lib/types/client/legacy/register-legacy-facets.js +0 -77
- package/lib/types/client/legacy/register-legacy-facets.js.map +0 -1
- package/lib/types/client/legacy/schedule.d.ts +0 -49
- package/lib/types/client/legacy/schedule.d.ts.map +0 -1
- package/lib/types/client/legacy/schedule.js +0 -73
- package/lib/types/client/legacy/schedule.js.map +0 -1
- package/lib/types/client/legacy/store-source.d.ts +0 -78
- package/lib/types/client/legacy/store-source.d.ts.map +0 -1
- package/lib/types/client/legacy/store-source.js +0 -82
- package/lib/types/client/legacy/store-source.js.map +0 -1
- package/lib/types/client/legacy/waiting-review.d.ts +0 -85
- package/lib/types/client/legacy/waiting-review.d.ts.map +0 -1
- package/lib/types/client/legacy/waiting-review.js +0 -179
- package/lib/types/client/legacy/waiting-review.js.map +0 -1
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* 把登记面读成「这一轮渲染该折哪些来源」的**唯一**一处接线。
|
|
3
|
+
*
|
|
4
|
+
* ## 为什么单独成文
|
|
5
|
+
*
|
|
6
|
+
* 这一步此前直接写在 `rows/WorkspaceBrowser.tsx` 里,两行:
|
|
7
|
+
*
|
|
8
|
+
* ```ts
|
|
9
|
+
* useSyncExternalStore(facetsStore.subscribe, facetsStore.getVersion, …) // 返回值丢掉
|
|
10
|
+
* const facets = useMemo(() => visibleFacets(facetsStore.list(), settings), [settings])
|
|
11
|
+
* ```
|
|
12
|
+
*
|
|
13
|
+
* 看着没问题——订阅了、也 memo 了。实际是**订阅通知只重渲染、不重算**:
|
|
14
|
+
* `useSyncExternalStore` 的返回值被丢掉,`useMemo` 的依赖里就没有任何东西随登记面变化,
|
|
15
|
+
* 于是那次重渲染原样拿回**上一次**的登记面。提供方在自己的 `apply` 里注册,而宿主不保证
|
|
16
|
+
* `apply` 与本组件首渲染的先后:注册**晚于**首渲染时,facet 明明登记上了,却永远进不了
|
|
17
|
+
* 徽标——不报错、不红测试(能渲染这条路径的那份上游 spec 在本仓库是跳过的,见
|
|
18
|
+
* `vitest.config.ts` 的 `MONOREPO_ONLY_SPECS`),只能靠刷新页面碰运气。
|
|
19
|
+
*
|
|
20
|
+
* 版本号必须**同时**当两件事用:① 触发重渲染的信号,② memo 的依赖。这里把它收进一个
|
|
21
|
+
* hook,让「只用①、丢掉②」在结构上写不出来,并且让这条接缝能被 `@testing-library/react`
|
|
22
|
+
* 直接覆盖(本文件零宿主 import,宿主依赖闭包进不来)。
|
|
23
|
+
*
|
|
24
|
+
* ## 为什么现在不再按设置筛
|
|
25
|
+
*
|
|
26
|
+
* 旧版本这里会过一道 `visibleFacets(list, settings)`,按 `facet.settingKey` 查本插件的
|
|
27
|
+
* 布尔开关。那意味着**本插件的配置面里写着别人家的语义**(`showScheduledInBadge` /
|
|
28
|
+
* `showWaitingReviewInBadge`,连图标形状都替对方写死),与"本插件不认识任何来源"直接
|
|
29
|
+
* 矛盾。现在外部来源的显隐归**来源自己**:它想被关掉就不注册 facet,登记面即所见。
|
|
30
|
+
* 本插件的开关只管自己那三档会话状态(见 `badge-settings.ts`)。
|
|
31
|
+
*
|
|
32
|
+
* @module dsh-group-status/client/use-registered-facets
|
|
33
|
+
*/
|
|
34
|
+
import { useMemo, useSyncExternalStore } from 'react';
|
|
35
|
+
/**
|
|
36
|
+
* 当前登记的来源,按登记面顺序(已按 `order` 排好)。
|
|
37
|
+
*
|
|
38
|
+
* 引用在版本号不变时保持稳定:登记面是低频事件,重算成本 = O(facet × 组内会话)。
|
|
39
|
+
*
|
|
40
|
+
* @param store - facet 消费侧存储(`facetStore()` 单例)。
|
|
41
|
+
*/
|
|
42
|
+
export function useRegisteredFacets(store) {
|
|
43
|
+
// `getVersion` 返回 number,引用天然稳定,不会像"每次新建一个快照对象"那样把订阅打成
|
|
44
|
+
// 死循环(React #185)。
|
|
45
|
+
const version = useSyncExternalStore(store.subscribe, store.getVersion, store.getServerVersion);
|
|
46
|
+
return useMemo(() => [...store.list()], [version]);
|
|
47
|
+
}
|
|
48
|
+
//# sourceMappingURL=use-registered-facets.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"use-registered-facets.js","sourceRoot":"","sources":["../../../src/client/use-registered-facets.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,OAAO,EAAE,OAAO,EAAE,oBAAoB,EAAE,MAAM,OAAO,CAAA;AAIrD;;;;;;GAMG;AACH,MAAM,UAAU,mBAAmB,CAAC,KAAiB;IACnD,uDAAuD;IACvD,mBAAmB;IACnB,MAAM,OAAO,GAAG,oBAAoB,CAAC,KAAK,CAAC,SAAS,EAAE,KAAK,CAAC,UAAU,EAAE,KAAK,CAAC,gBAAgB,CAAC,CAAA;IAC/F,OAAO,OAAO,CAAC,GAAG,EAAE,CAAC,CAAC,GAAG,KAAK,CAAC,IAAI,EAAE,CAAC,EAAE,CAAC,OAAO,CAAC,CAAC,CAAA;AACpD,CAAC"}
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* 宿主契约的**解析与比对** —— 一份实现,两个调用方:
|
|
3
|
+
*
|
|
4
|
+
* - `scripts/check-upstream.ts`(tsx,跑给人看的那道闸,联网时还能查 npm 最新发布版);
|
|
5
|
+
* - `tests/host-pending-kinds.node.test.mjs`(`npm test` 里的离线那道闸,CI 会跑)。
|
|
6
|
+
*
|
|
7
|
+
* ## 我们到底依赖宿主的什么
|
|
8
|
+
*
|
|
9
|
+
* 本仓库的 `src/client/tree.ts` 是宿主 `@deepseek-ai/dsh-client-ui-workspace` 投影的
|
|
10
|
+
* **fork**(为了在分组聚合里加 facet 贡献)。那份 fork 里真正会**静默坏掉**的地方只有
|
|
11
|
+
* 一处:`pendingInteraction.kind`。
|
|
12
|
+
*
|
|
13
|
+
* - 它是**开放集合**:`SessionPendingInteractionMap` 靠声明合并扩展,任何宿主包都能贡献
|
|
14
|
+
* 自己的 kind。宿主当前的 `visiblePendingKind` 认三个(`approval` / `plan-review` /
|
|
15
|
+
* `question`),并把没认出来的 kind **悄悄丢掉**。
|
|
16
|
+
* - 宿主新增一种 kind 时,**宿主侧栏与我们的徽标会一起不显示它**(两边口径一致,不是我们
|
|
17
|
+
* 的错),但我们要**知道**这件事好跟上;没跟上,两边一起不显示,用户只会觉得"这俩对不上"。
|
|
18
|
+
* - 反过来**不要自己多认**:宿主不画的我们画了,徽标与宿主侧栏就成了两套事实。
|
|
19
|
+
*
|
|
20
|
+
* 另有两个状态事实:宿主若把 `completionUnread`(「已完成」绿点)或 `pendingInteraction`
|
|
21
|
+
* (「待审批」黄点)改名,我们的 fork 会**静默地**再也不画那一类状态 —— 同样不报错。
|
|
22
|
+
*
|
|
23
|
+
* @module dsh-group-status/host-contract
|
|
24
|
+
*/
|
|
25
|
+
/** 我们从宿主读的两个状态事实:它们改名了,这份 fork 就会静默失效。 */
|
|
26
|
+
export declare const HOST_STATUS_FACTS: readonly ["completionUnread", "pendingInteraction"];
|
|
27
|
+
/** 一处契约漂移。 */
|
|
28
|
+
export interface ContractDrift {
|
|
29
|
+
readonly kind: 'kind-set' | 'fact-missing';
|
|
30
|
+
readonly detail: string;
|
|
31
|
+
}
|
|
32
|
+
/** 从宿主实现里读出来的契约。 */
|
|
33
|
+
export interface HostContract {
|
|
34
|
+
/** 宿主认的待处理 kind 集合。 */
|
|
35
|
+
readonly kinds: readonly string[];
|
|
36
|
+
/** 宿主 bundle 里是否还找得到那两个状态事实。 */
|
|
37
|
+
readonly facts: Readonly<Record<(typeof HOST_STATUS_FACTS)[number], boolean>>;
|
|
38
|
+
}
|
|
39
|
+
/**
|
|
40
|
+
* 从宿主实现(发布产物 `lib/client.js` 的文本)里抠出 `visiblePendingKind` 认的 kind。
|
|
41
|
+
*
|
|
42
|
+
* 抠不出来 = 上游改了实现形状 → 抛错,不静默放过:空集合会让"集合相等"变成永远成立。
|
|
43
|
+
* @param source - 宿主 bundle 文本。
|
|
44
|
+
*/
|
|
45
|
+
export declare function parseHostPendingKinds(source: string): string[];
|
|
46
|
+
/**
|
|
47
|
+
* 读一份宿主 bundle,抽出契约点。
|
|
48
|
+
* @param source - 宿主 bundle 文本。
|
|
49
|
+
*/
|
|
50
|
+
export declare function readHostContract(source: string): HostContract;
|
|
51
|
+
/**
|
|
52
|
+
* 比对我们认的 kind 与宿主认的 kind,以及宿主是否还带着我们要读的事实。
|
|
53
|
+
* @param ours - 本插件认的 kind。
|
|
54
|
+
* @param host - 宿主契约。
|
|
55
|
+
*/
|
|
56
|
+
export declare function compareHostContract(ours: readonly string[], host: HostContract): ContractDrift[];
|
|
57
|
+
//# sourceMappingURL=host-contract.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"host-contract.d.ts","sourceRoot":"","sources":["../../src/host-contract.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,0CAA0C;AAC1C,eAAO,MAAM,iBAAiB,qDAAsD,CAAA;AAKpF,cAAc;AACd,MAAM,WAAW,aAAa;IAC5B,QAAQ,CAAC,IAAI,EAAE,UAAU,GAAG,cAAc,CAAA;IAC1C,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAA;CACxB;AAED,oBAAoB;AACpB,MAAM,WAAW,YAAY;IAC3B,uBAAuB;IACvB,QAAQ,CAAC,KAAK,EAAE,SAAS,MAAM,EAAE,CAAA;IACjC,gCAAgC;IAChC,QAAQ,CAAC,KAAK,EAAE,QAAQ,CAAC,MAAM,CAAC,CAAC,OAAO,iBAAiB,CAAC,CAAC,MAAM,CAAC,EAAE,OAAO,CAAC,CAAC,CAAA;CAC9E;AAED;;;;;GAKG;AACH,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,EAAE,CAc9D;AAED;;;GAGG;AACH,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,MAAM,GAAG,YAAY,CAM7D;AAED;;;;GAIG;AACH,wBAAgB,mBAAmB,CAAC,IAAI,EAAE,SAAS,MAAM,EAAE,EAAE,IAAI,EAAE,YAAY,GAAG,aAAa,EAAE,CAkBhG"}
|
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* 宿主契约的**解析与比对** —— 一份实现,两个调用方:
|
|
3
|
+
*
|
|
4
|
+
* - `scripts/check-upstream.ts`(tsx,跑给人看的那道闸,联网时还能查 npm 最新发布版);
|
|
5
|
+
* - `tests/host-pending-kinds.node.test.mjs`(`npm test` 里的离线那道闸,CI 会跑)。
|
|
6
|
+
*
|
|
7
|
+
* ## 我们到底依赖宿主的什么
|
|
8
|
+
*
|
|
9
|
+
* 本仓库的 `src/client/tree.ts` 是宿主 `@deepseek-ai/dsh-client-ui-workspace` 投影的
|
|
10
|
+
* **fork**(为了在分组聚合里加 facet 贡献)。那份 fork 里真正会**静默坏掉**的地方只有
|
|
11
|
+
* 一处:`pendingInteraction.kind`。
|
|
12
|
+
*
|
|
13
|
+
* - 它是**开放集合**:`SessionPendingInteractionMap` 靠声明合并扩展,任何宿主包都能贡献
|
|
14
|
+
* 自己的 kind。宿主当前的 `visiblePendingKind` 认三个(`approval` / `plan-review` /
|
|
15
|
+
* `question`),并把没认出来的 kind **悄悄丢掉**。
|
|
16
|
+
* - 宿主新增一种 kind 时,**宿主侧栏与我们的徽标会一起不显示它**(两边口径一致,不是我们
|
|
17
|
+
* 的错),但我们要**知道**这件事好跟上;没跟上,两边一起不显示,用户只会觉得"这俩对不上"。
|
|
18
|
+
* - 反过来**不要自己多认**:宿主不画的我们画了,徽标与宿主侧栏就成了两套事实。
|
|
19
|
+
*
|
|
20
|
+
* 另有两个状态事实:宿主若把 `completionUnread`(「已完成」绿点)或 `pendingInteraction`
|
|
21
|
+
* (「待审批」黄点)改名,我们的 fork 会**静默地**再也不画那一类状态 —— 同样不报错。
|
|
22
|
+
*
|
|
23
|
+
* @module dsh-group-status/host-contract
|
|
24
|
+
*/
|
|
25
|
+
/** 我们从宿主读的两个状态事实:它们改名了,这份 fork 就会静默失效。 */
|
|
26
|
+
export const HOST_STATUS_FACTS = ['completionUnread', 'pendingInteraction'];
|
|
27
|
+
/** 宿主实现里那个函数的形状(我们这份 fork 是照它抄的,所以两边可比)。 */
|
|
28
|
+
const VISIBLE_PENDING_KIND = /function visiblePendingKind\s*\([^)]*\)\s*\{\s*switch\s*\([^)]*\)\s*\{([\s\S]*?)\n\s*\}/;
|
|
29
|
+
/**
|
|
30
|
+
* 从宿主实现(发布产物 `lib/client.js` 的文本)里抠出 `visiblePendingKind` 认的 kind。
|
|
31
|
+
*
|
|
32
|
+
* 抠不出来 = 上游改了实现形状 → 抛错,不静默放过:空集合会让"集合相等"变成永远成立。
|
|
33
|
+
* @param source - 宿主 bundle 文本。
|
|
34
|
+
*/
|
|
35
|
+
export function parseHostPendingKinds(source) {
|
|
36
|
+
const found = VISIBLE_PENDING_KIND.exec(source);
|
|
37
|
+
if (!found) {
|
|
38
|
+
throw new Error('宿主实现里找不到 `visiblePendingKind` —— 上游改了实现形状,守卫与本脚本都要跟着改');
|
|
39
|
+
}
|
|
40
|
+
const body = found[1];
|
|
41
|
+
if (body === undefined) {
|
|
42
|
+
throw new Error('宿主实现里 `visiblePendingKind` 的函数体没抠出来 —— 上游改了实现形状,守卫与本脚本都要跟着改');
|
|
43
|
+
}
|
|
44
|
+
const kinds = [];
|
|
45
|
+
for (const match of body.matchAll(/case\s+"([^"]+)"/g)) {
|
|
46
|
+
if (match[1] !== undefined)
|
|
47
|
+
kinds.push(match[1]);
|
|
48
|
+
}
|
|
49
|
+
return kinds;
|
|
50
|
+
}
|
|
51
|
+
/**
|
|
52
|
+
* 读一份宿主 bundle,抽出契约点。
|
|
53
|
+
* @param source - 宿主 bundle 文本。
|
|
54
|
+
*/
|
|
55
|
+
export function readHostContract(source) {
|
|
56
|
+
const kinds = parseHostPendingKinds(source);
|
|
57
|
+
const facts = Object.fromEntries(HOST_STATUS_FACTS.map(fact => [fact, source.includes(fact)]));
|
|
58
|
+
return { kinds, facts };
|
|
59
|
+
}
|
|
60
|
+
/**
|
|
61
|
+
* 比对我们认的 kind 与宿主认的 kind,以及宿主是否还带着我们要读的事实。
|
|
62
|
+
* @param ours - 本插件认的 kind。
|
|
63
|
+
* @param host - 宿主契约。
|
|
64
|
+
*/
|
|
65
|
+
export function compareHostContract(ours, host) {
|
|
66
|
+
const drifts = [];
|
|
67
|
+
const missing = host.kinds.filter(kind => !ours.includes(kind));
|
|
68
|
+
const extra = ours.filter(kind => !host.kinds.includes(kind));
|
|
69
|
+
if (missing.length > 0 || extra.length > 0) {
|
|
70
|
+
drifts.push({
|
|
71
|
+
kind: 'kind-set',
|
|
72
|
+
detail: `宿主认 [${host.kinds.join(', ')}],我们认 [${ours.join(', ')}]`
|
|
73
|
+
+ (missing.length > 0 ? `;宿主多了:${missing.join(', ')}` : '')
|
|
74
|
+
+ (extra.length > 0 ? `;我们多认了:${extra.join(', ')}` : ''),
|
|
75
|
+
});
|
|
76
|
+
}
|
|
77
|
+
for (const fact of HOST_STATUS_FACTS) {
|
|
78
|
+
if (!host.facts[fact]) {
|
|
79
|
+
drifts.push({ kind: 'fact-missing', detail: `宿主实现里找不到 \`${fact}\`(它改名或改了形状)` });
|
|
80
|
+
}
|
|
81
|
+
}
|
|
82
|
+
return drifts;
|
|
83
|
+
}
|
|
84
|
+
//# sourceMappingURL=host-contract.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"host-contract.js","sourceRoot":"","sources":["../../src/host-contract.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,0CAA0C;AAC1C,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,kBAAkB,EAAE,oBAAoB,CAAU,CAAA;AAEpF,4CAA4C;AAC5C,MAAM,oBAAoB,GAAG,yFAAyF,CAAA;AAgBtH;;;;;GAKG;AACH,MAAM,UAAU,qBAAqB,CAAC,MAAc;IAClD,MAAM,KAAK,GAAG,oBAAoB,CAAC,IAAI,CAAC,MAAM,CAAC,CAAA;IAC/C,IAAI,CAAC,KAAK,EAAE,CAAC;QACX,MAAM,IAAI,KAAK,CAAC,uDAAuD,CAAC,CAAA;IAC1E,CAAC;IACD,MAAM,IAAI,GAAG,KAAK,CAAC,CAAC,CAAC,CAAA;IACrB,IAAI,IAAI,KAAK,SAAS,EAAE,CAAC;QACvB,MAAM,IAAI,KAAK,CAAC,6DAA6D,CAAC,CAAA;IAChF,CAAC;IACD,MAAM,KAAK,GAAa,EAAE,CAAA;IAC1B,KAAK,MAAM,KAAK,IAAI,IAAI,CAAC,QAAQ,CAAC,mBAAmB,CAAC,EAAE,CAAC;QACvD,IAAI,KAAK,CAAC,CAAC,CAAC,KAAK,SAAS;YAAE,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAA;IAClD,CAAC;IACD,OAAO,KAAK,CAAA;AACd,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,gBAAgB,CAAC,MAAc;IAC7C,MAAM,KAAK,GAAG,qBAAqB,CAAC,MAAM,CAAC,CAAA;IAC3C,MAAM,KAAK,GAAG,MAAM,CAAC,WAAW,CAC9B,iBAAiB,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,IAAI,EAAE,MAAM,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC,CACN,CAAA;IACxD,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,CAAA;AACzB,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,mBAAmB,CAAC,IAAuB,EAAE,IAAkB;IAC7E,MAAM,MAAM,GAAoB,EAAE,CAAA;IAClC,MAAM,OAAO,GAAG,IAAI,CAAC,KAAK,CAAC,MAAM,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAA;IAC/D,MAAM,KAAK,GAAG,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAA;IAC7D,IAAI,OAAO,CAAC,MAAM,GAAG,CAAC,IAAI,KAAK,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC3C,MAAM,CAAC,IAAI,CAAC;YACV,IAAI,EAAE,UAAU;YAChB,MAAM,EAAE,QAAQ,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,UAAU,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG;kBAC7D,CAAC,OAAO,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,SAAS,OAAO,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;kBACzD,CAAC,KAAK,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,UAAU,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SAC3D,CAAC,CAAA;IACJ,CAAC;IACD,KAAK,MAAM,IAAI,IAAI,iBAAiB,EAAE,CAAC;QACrC,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC;YACtB,MAAM,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,cAAc,EAAE,MAAM,EAAE,cAAc,IAAI,cAAc,EAAE,CAAC,CAAA;QACjF,CAAC;IACH,CAAC;IACD,OAAO,MAAM,CAAA;AACf,CAAC"}
|
package/lib/types/index.d.ts
CHANGED
|
@@ -23,6 +23,13 @@ export declare const name = "dsh-group-status";
|
|
|
23
23
|
* 读取同一份文档,改完即时生效、无需刷新。
|
|
24
24
|
*
|
|
25
25
|
* 全部可选且带默认值:未配置时即开箱即用(所有来源默认显示)。
|
|
26
|
+
*
|
|
27
|
+
* ⚠️ **这里只允许出现本插件自己的语义**。历史上曾有 `showScheduledInBadge` /
|
|
28
|
+
* `showWaitingReviewInBadge` 两个字段,名字与图标形状都替别人家插件写死(定时任务来自
|
|
29
|
+
* dsh-later、等待评审来自 dsh-gitea-dispatch)—— 与本插件「不认识任何具体来源」的立身
|
|
30
|
+
* 之本直接矛盾。外部来源的显隐现在归**来源自己**:它想被关掉就不注册 facet(协议文档
|
|
31
|
+
* 「显隐归谁」一节)。删字段是一次**破坏性配置变更**:旧值不再被读取,等同回到默认
|
|
32
|
+
* "显示"(默认全开,所以最坏情况是"某个来源重新出现",不会留下坏数据)。
|
|
26
33
|
*/
|
|
27
34
|
export declare const Config: Schema<NoInfer<Schemastery.ObjectS<NoInfer<{
|
|
28
35
|
/**
|
|
@@ -36,10 +43,6 @@ export declare const Config: Schema<NoInfer<Schemastery.ObjectS<NoInfer<{
|
|
|
36
43
|
showRunningInBadge: Schema<boolean, boolean, "defined">;
|
|
37
44
|
/** 折叠分组徽标是否显示「待审批」黄点(approval / plan-review / question)。 */
|
|
38
45
|
showPendingInBadge: Schema<boolean, boolean, "defined">;
|
|
39
|
-
/** 折叠分组徽标是否显示「定时任务」时钟图标(数据来自 dsh-later)。 */
|
|
40
|
-
showScheduledInBadge: Schema<boolean, boolean, "defined">;
|
|
41
|
-
/** 折叠分组徽标是否显示「等待评审」沙漏图标(数据来自 dsh-gitea-dispatch)。 */
|
|
42
|
-
showWaitingReviewInBadge: Schema<boolean, boolean, "defined">;
|
|
43
46
|
/** 悬停卡里是否显示聚合明细行("1 等待回答 · 1 进行中…")。 */
|
|
44
47
|
showHoverDetails: Schema<boolean, boolean, "defined">;
|
|
45
48
|
/** 徽标数字显示阈值:数量 >= 此值时才显示数字(默认 2,即 count=1 时省略)。 */
|
|
@@ -56,10 +59,6 @@ export declare const Config: Schema<NoInfer<Schemastery.ObjectS<NoInfer<{
|
|
|
56
59
|
showRunningInBadge: Schema<boolean, boolean, "defined">;
|
|
57
60
|
/** 折叠分组徽标是否显示「待审批」黄点(approval / plan-review / question)。 */
|
|
58
61
|
showPendingInBadge: Schema<boolean, boolean, "defined">;
|
|
59
|
-
/** 折叠分组徽标是否显示「定时任务」时钟图标(数据来自 dsh-later)。 */
|
|
60
|
-
showScheduledInBadge: Schema<boolean, boolean, "defined">;
|
|
61
|
-
/** 折叠分组徽标是否显示「等待评审」沙漏图标(数据来自 dsh-gitea-dispatch)。 */
|
|
62
|
-
showWaitingReviewInBadge: Schema<boolean, boolean, "defined">;
|
|
63
62
|
/** 悬停卡里是否显示聚合明细行("1 等待回答 · 1 进行中…")。 */
|
|
64
63
|
showHoverDetails: Schema<boolean, boolean, "defined">;
|
|
65
64
|
/** 徽标数字显示阈值:数量 >= 此值时才显示数字(默认 2,即 count=1 时省略)。 */
|
|
@@ -70,8 +69,6 @@ export interface Config {
|
|
|
70
69
|
showCompletedInBadge: boolean;
|
|
71
70
|
showRunningInBadge: boolean;
|
|
72
71
|
showPendingInBadge: boolean;
|
|
73
|
-
showScheduledInBadge: boolean;
|
|
74
|
-
showWaitingReviewInBadge: boolean;
|
|
75
72
|
showHoverDetails: boolean;
|
|
76
73
|
countThreshold: number;
|
|
77
74
|
}
|
package/lib/types/index.d.ts.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,OAAO,MAAM,MAAM,0BAA0B,CAAA;AAE7C,4EAA4E;AAC5E,eAAO,MAAM,IAAI,qBAAqB,CAAA;AAEtC
|
|
1
|
+
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,OAAO,MAAM,MAAM,0BAA0B,CAAA;AAE7C,4EAA4E;AAC5E,eAAO,MAAM,IAAI,qBAAqB,CAAA;AAEtC;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,MAAM;IACjB;;;;;OAKG;;IAEH,gCAAgC;;IAEhC,4DAA4D;;IAE5D,wCAAwC;;IAExC,mDAAmD;;;IAbnD;;;;;OAKG;;IAEH,gCAAgC;;IAEhC,4DAA4D;;IAE5D,wCAAwC;;IAExC,mDAAmD;;iBAExC,CAAA;AAEb,uDAAuD;AACvD,MAAM,WAAW,MAAM;IACrB,oBAAoB,EAAE,OAAO,CAAA;IAC7B,kBAAkB,EAAE,OAAO,CAAA;IAC3B,kBAAkB,EAAE,OAAO,CAAA;IAC3B,gBAAgB,EAAE,OAAO,CAAA;IACzB,cAAc,EAAE,MAAM,CAAA;CACvB;AAED;;;;;;GAMG;AACH,wBAAgB,KAAK,CAAC,IAAI,EAAE,OAAO,EAAE,OAAO,EAAE,MAAM,GAAG,IAAI,CAAG"}
|
package/lib/types/index.js
CHANGED
|
@@ -23,6 +23,13 @@ export const name = 'dsh-group-status';
|
|
|
23
23
|
* 读取同一份文档,改完即时生效、无需刷新。
|
|
24
24
|
*
|
|
25
25
|
* 全部可选且带默认值:未配置时即开箱即用(所有来源默认显示)。
|
|
26
|
+
*
|
|
27
|
+
* ⚠️ **这里只允许出现本插件自己的语义**。历史上曾有 `showScheduledInBadge` /
|
|
28
|
+
* `showWaitingReviewInBadge` 两个字段,名字与图标形状都替别人家插件写死(定时任务来自
|
|
29
|
+
* dsh-later、等待评审来自 dsh-gitea-dispatch)—— 与本插件「不认识任何具体来源」的立身
|
|
30
|
+
* 之本直接矛盾。外部来源的显隐现在归**来源自己**:它想被关掉就不注册 facet(协议文档
|
|
31
|
+
* 「显隐归谁」一节)。删字段是一次**破坏性配置变更**:旧值不再被读取,等同回到默认
|
|
32
|
+
* "显示"(默认全开,所以最坏情况是"某个来源重新出现",不会留下坏数据)。
|
|
26
33
|
*/
|
|
27
34
|
export const Config = Schema.object({
|
|
28
35
|
/**
|
|
@@ -36,10 +43,6 @@ export const Config = Schema.object({
|
|
|
36
43
|
showRunningInBadge: Schema.boolean().default(true),
|
|
37
44
|
/** 折叠分组徽标是否显示「待审批」黄点(approval / plan-review / question)。 */
|
|
38
45
|
showPendingInBadge: Schema.boolean().default(true),
|
|
39
|
-
/** 折叠分组徽标是否显示「定时任务」时钟图标(数据来自 dsh-later)。 */
|
|
40
|
-
showScheduledInBadge: Schema.boolean().default(true),
|
|
41
|
-
/** 折叠分组徽标是否显示「等待评审」沙漏图标(数据来自 dsh-gitea-dispatch)。 */
|
|
42
|
-
showWaitingReviewInBadge: Schema.boolean().default(true),
|
|
43
46
|
/** 悬停卡里是否显示聚合明细行("1 等待回答 · 1 进行中…")。 */
|
|
44
47
|
showHoverDetails: Schema.boolean().default(true),
|
|
45
48
|
/** 徽标数字显示阈值:数量 >= 此值时才显示数字(默认 2,即 count=1 时省略)。 */
|
package/lib/types/index.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,OAAO,MAAM,MAAM,0BAA0B,CAAA;AAE7C,4EAA4E;AAC5E,MAAM,CAAC,MAAM,IAAI,GAAG,kBAAkB,CAAA;AAEtC
|
|
1
|
+
{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,OAAO,MAAM,MAAM,0BAA0B,CAAA;AAE7C,4EAA4E;AAC5E,MAAM,CAAC,MAAM,IAAI,GAAG,kBAAkB,CAAA;AAEtC;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,MAAM,GAAG,MAAM,CAAC,MAAM,CAAC;IAClC;;;;;OAKG;IACH,oBAAoB,EAAE,MAAM,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC;IACpD,gCAAgC;IAChC,kBAAkB,EAAE,MAAM,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC;IAClD,4DAA4D;IAC5D,kBAAkB,EAAE,MAAM,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC;IAClD,wCAAwC;IACxC,gBAAgB,EAAE,MAAM,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC;IAChD,mDAAmD;IACnD,cAAc,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC,OAAO,CAAC,CAAC,CAAC;CAC3C,CAAC,CAAC,QAAQ,EAAE,CAAA;AAWb;;;;;;GAMG;AACH,MAAM,UAAU,KAAK,CAAC,IAAa,EAAE,OAAe,IAAS,CAAC"}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-group-status",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.5.0",
|
|
4
4
|
"description": "DSH 侧栏折叠分组聚合徽标:收起的文件夹行显示进行中/待审批/已完成/定时任务/等待评审的聚合状态,带数字与悬停明细。",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"dsh",
|
|
@@ -22,7 +22,8 @@
|
|
|
22
22
|
"url": "https://github.com/dsh-plugin-collection/dsh-group-status/issues"
|
|
23
23
|
},
|
|
24
24
|
"engines": {
|
|
25
|
-
"node": "^22.19 || >=24"
|
|
25
|
+
"node": "^22.19 || >=24",
|
|
26
|
+
"dsh": ">=0.2.1-rc.2 <0.3.0-0"
|
|
26
27
|
},
|
|
27
28
|
"type": "module",
|
|
28
29
|
"icon": "./icon.svg",
|
|
@@ -46,6 +47,7 @@
|
|
|
46
47
|
},
|
|
47
48
|
"client": {
|
|
48
49
|
"inject": [
|
|
50
|
+
"@deepseek-ai/dsh-api-remote-access",
|
|
49
51
|
"@deepseek-ai/dsh-api-remotes",
|
|
50
52
|
"@deepseek-ai/dsh-api-session-controller",
|
|
51
53
|
"@deepseek-ai/dsh-api-workspace-controller",
|
|
@@ -62,38 +64,40 @@
|
|
|
62
64
|
}
|
|
63
65
|
},
|
|
64
66
|
"peerDependencies": {
|
|
65
|
-
"@deepseek-ai/cordis": "~4.0.
|
|
67
|
+
"@deepseek-ai/cordis": "~4.0.5"
|
|
66
68
|
},
|
|
67
69
|
"dependencies": {
|
|
68
|
-
"@deepseek-ai/schemastery": "
|
|
70
|
+
"@deepseek-ai/schemastery": "~3.18.5"
|
|
69
71
|
},
|
|
70
72
|
"devDependencies": {
|
|
71
|
-
"@deepseek-ai/cordis": "~4.0.
|
|
72
|
-
"@deepseek-ai/dsh-agent": "0.2.
|
|
73
|
-
"@deepseek-ai/dsh-api-
|
|
74
|
-
"@deepseek-ai/dsh-api-
|
|
75
|
-
"@deepseek-ai/dsh-api-
|
|
76
|
-
"@deepseek-ai/dsh-
|
|
77
|
-
"@deepseek-ai/dsh-client-
|
|
78
|
-
"@deepseek-ai/dsh-client-
|
|
79
|
-
"@deepseek-ai/dsh-client-
|
|
80
|
-
"@deepseek-ai/dsh-client-
|
|
81
|
-
"@deepseek-ai/dsh-client-
|
|
82
|
-
"@deepseek-ai/dsh-client-
|
|
83
|
-
"@deepseek-ai/dsh-client-ui-
|
|
84
|
-
"@deepseek-ai/dsh-client-ui-
|
|
85
|
-
"@deepseek-ai/dsh-client-ui-
|
|
86
|
-
"@deepseek-ai/dsh-client-ui-
|
|
87
|
-
"@deepseek-ai/dsh-client-ui-
|
|
88
|
-
"@deepseek-ai/dsh-client-ui-
|
|
89
|
-
"@deepseek-ai/dsh-
|
|
90
|
-
"@deepseek-ai/dsh-
|
|
91
|
-
"@deepseek-ai/dsh-
|
|
92
|
-
"@deepseek-ai/dsh-
|
|
93
|
-
"@deepseek-ai/dsh-
|
|
94
|
-
"@deepseek-ai/dsh-
|
|
95
|
-
"@deepseek-ai/dsh-
|
|
96
|
-
"@deepseek-ai/
|
|
73
|
+
"@deepseek-ai/cordis": "~4.0.5",
|
|
74
|
+
"@deepseek-ai/dsh-agent": "0.2.1-rc.2",
|
|
75
|
+
"@deepseek-ai/dsh-api-remote-access": "0.2.1-rc.2",
|
|
76
|
+
"@deepseek-ai/dsh-api-remotes": "0.2.1-rc.2",
|
|
77
|
+
"@deepseek-ai/dsh-api-session-controller": "0.2.1-rc.2",
|
|
78
|
+
"@deepseek-ai/dsh-api-workspace-controller": "0.2.1-rc.2",
|
|
79
|
+
"@deepseek-ai/dsh-client-connection": "0.2.1-rc.2",
|
|
80
|
+
"@deepseek-ai/dsh-client-locale": "0.2.1-rc.2",
|
|
81
|
+
"@deepseek-ai/dsh-client-product-analytics": "0.2.1-rc.2",
|
|
82
|
+
"@deepseek-ai/dsh-client-shortcuts": "0.2.1-rc.2",
|
|
83
|
+
"@deepseek-ai/dsh-client-store": "0.2.1-rc.2",
|
|
84
|
+
"@deepseek-ai/dsh-client-test-runtime": "0.2.1-rc.2",
|
|
85
|
+
"@deepseek-ai/dsh-client-ui-conversation": "0.2.1-rc.2",
|
|
86
|
+
"@deepseek-ai/dsh-client-ui-layout": "0.2.1-rc.2",
|
|
87
|
+
"@deepseek-ai/dsh-client-ui-primitives": "0.2.1-rc.2",
|
|
88
|
+
"@deepseek-ai/dsh-client-ui-renderer": "0.2.1-rc.2",
|
|
89
|
+
"@deepseek-ai/dsh-client-ui-session": "0.2.1-rc.2",
|
|
90
|
+
"@deepseek-ai/dsh-client-ui-sidebar": "0.2.1-rc.2",
|
|
91
|
+
"@deepseek-ai/dsh-client-ui-slots": "0.2.1-rc.2",
|
|
92
|
+
"@deepseek-ai/dsh-client-ui-workspace": "0.2.1-rc.2",
|
|
93
|
+
"@deepseek-ai/dsh-jobs": "0.2.1-rc.2",
|
|
94
|
+
"@deepseek-ai/dsh-schedule": "0.2.1-rc.2",
|
|
95
|
+
"@deepseek-ai/dsh-session": "0.2.1-rc.2",
|
|
96
|
+
"@deepseek-ai/dsh-subagent": "0.2.1-rc.2",
|
|
97
|
+
"@deepseek-ai/dsh-typert-protocol": "0.2.1-rc.2",
|
|
98
|
+
"@deepseek-ai/dsh-util-values": "0.2.1-rc.2",
|
|
99
|
+
"@deepseek-ai/dsh-util-workspace-path": "0.2.1-rc.2",
|
|
100
|
+
"@deepseek-ai/schemastery": "~3.18.5",
|
|
97
101
|
"@testing-library/react": "16.3.3",
|
|
98
102
|
"@types/react": "~18.3.1",
|
|
99
103
|
"clsx": "^2.0.0",
|
|
@@ -1,17 +0,0 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* 按用户设置筛掉不参与折叠的状态来源。
|
|
3
|
-
*
|
|
4
|
-
* 单独成文是因为它属于**徽标自身**的可见性规则,而不是某个来源的适配:来源只在
|
|
5
|
-
* `facet.settingKey` 上声明"我受哪个开关管",开关的语义与过滤时机归本插件。
|
|
6
|
-
*
|
|
7
|
-
* 过滤发生在**折叠之前**而不是渲染阶段:徽标数字、图标、`aria-label`、悬停明细与
|
|
8
|
-
* "要不要画徽标"因此天然同源。放到渲染阶段会出现"label 里有、计数里没有",而那正是
|
|
9
|
-
* 徽标最容易被怀疑撒谎的地方。
|
|
10
|
-
*
|
|
11
|
-
* @module dsh-group-status/client/facet-visibility
|
|
12
|
-
*/
|
|
13
|
-
import { type ResolvedBadgeSettings } from './badge-settings.ts';
|
|
14
|
-
import type { RegisteredFacet } from './facets.ts';
|
|
15
|
-
/** 筛出设置允许显示的登记项;顺序保持登记面的顺序(已按 `order` 排好)。 */
|
|
16
|
-
export declare function visibleFacets(entries: readonly RegisteredFacet[], settings: ResolvedBadgeSettings): RegisteredFacet[];
|
|
17
|
-
//# sourceMappingURL=facet-visibility.d.ts.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"facet-visibility.d.ts","sourceRoot":"","sources":["../../../src/client/facet-visibility.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,OAAO,EAA0B,KAAK,qBAAqB,EAAE,MAAM,qBAAqB,CAAA;AACxF,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,aAAa,CAAA;AAElD,8CAA8C;AAC9C,wBAAgB,aAAa,CAC3B,OAAO,EAAE,SAAS,eAAe,EAAE,EACnC,QAAQ,EAAE,qBAAqB,GAC9B,eAAe,EAAE,CAEnB"}
|
|
@@ -1,18 +0,0 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* 按用户设置筛掉不参与折叠的状态来源。
|
|
3
|
-
*
|
|
4
|
-
* 单独成文是因为它属于**徽标自身**的可见性规则,而不是某个来源的适配:来源只在
|
|
5
|
-
* `facet.settingKey` 上声明"我受哪个开关管",开关的语义与过滤时机归本插件。
|
|
6
|
-
*
|
|
7
|
-
* 过滤发生在**折叠之前**而不是渲染阶段:徽标数字、图标、`aria-label`、悬停明细与
|
|
8
|
-
* "要不要画徽标"因此天然同源。放到渲染阶段会出现"label 里有、计数里没有",而那正是
|
|
9
|
-
* 徽标最容易被怀疑撒谎的地方。
|
|
10
|
-
*
|
|
11
|
-
* @module dsh-group-status/client/facet-visibility
|
|
12
|
-
*/
|
|
13
|
-
import { facetVisibleBySettings } from "./badge-settings.js";
|
|
14
|
-
/** 筛出设置允许显示的登记项;顺序保持登记面的顺序(已按 `order` 排好)。 */
|
|
15
|
-
export function visibleFacets(entries, settings) {
|
|
16
|
-
return entries.filter(entry => facetVisibleBySettings(settings, entry.facet.settingKey));
|
|
17
|
-
}
|
|
18
|
-
//# sourceMappingURL=facet-visibility.js.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"facet-visibility.js","sourceRoot":"","sources":["../../../src/client/facet-visibility.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,OAAO,EAAE,sBAAsB,EAA8B,MAAM,qBAAqB,CAAA;AAGxF,8CAA8C;AAC9C,MAAM,UAAU,aAAa,CAC3B,OAAmC,EACnC,QAA+B;IAE/B,OAAO,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,sBAAsB,CAAC,QAAQ,EAAE,KAAK,CAAC,KAAK,CAAC,UAAU,CAAC,CAAC,CAAA;AAC1F,CAAC"}
|
|
@@ -1,30 +0,0 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* 过渡期的跨插件桥:把 dsh-later / dsh-gitea-dispatch 的摘要面接到 facet 登记面上。
|
|
3
|
-
*
|
|
4
|
-
* ⚠️ 本目录整体是**临时代管**。两个提供方按 `../facets.ts` 的协议自己注册之后
|
|
5
|
-
* (对应它们各自的 issue),`legacy/` 整个目录与 `package.json` 里的
|
|
6
|
-
* `dsh.client.external` 两条声明一并删除,本插件不再认识任何具体状态源。
|
|
7
|
-
*
|
|
8
|
-
* ## 为什么在这里、又为什么要"登记表"
|
|
9
|
-
*
|
|
10
|
-
* 两家的 store 都在自己的 client `apply` 里创建,而**插件 apply 的先后宿主不保证**:
|
|
11
|
-
* 本插件可能在对方 store 就绪之前就开始渲染。所以桥接层不能一次性抓 store,必须
|
|
12
|
-
* 订阅对方的"store 登记变化",并把 store 的迟到本身当作一次快照变化通知出去
|
|
13
|
-
* (`subscribe` 里同时挂两层)。这与 `cross-plugin-summary.ts` 里 `createSummaryRegistry`
|
|
14
|
-
* 解决的是一模一样的问题,只是这次藏在桥接层里,不污染协议。
|
|
15
|
-
*
|
|
16
|
-
* ## 为什么用 subscribe/getSnapshot 而不是调对方的 hook
|
|
17
|
-
*
|
|
18
|
-
* 见 `../facets.ts` 文件头:hook 数量必须逐次渲染恒定,而 facet 运行时可增删。桥接层
|
|
19
|
-
* 只要把对方的 store 面交出去,聚合侧就完全不需要知道背后有几个来源。
|
|
20
|
-
*
|
|
21
|
-
* @module dsh-group-status/client/legacy/bridge
|
|
22
|
-
*/
|
|
23
|
-
import { type FacetRegistry, type Unregister } from '../facets.ts';
|
|
24
|
-
/**
|
|
25
|
-
* 安装过渡适配器。
|
|
26
|
-
*
|
|
27
|
-
* @param target - 登记面;缺省用生产单例,测试传入自建实例以隔离。
|
|
28
|
-
*/
|
|
29
|
-
export declare function installLegacyBridges(target?: FacetRegistry): Unregister;
|
|
30
|
-
//# sourceMappingURL=bridge.d.ts.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"bridge.d.ts","sourceRoot":"","sources":["../../../../src/client/legacy/bridge.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,OAAO,EAAY,KAAK,aAAa,EAAE,KAAK,UAAU,EAAE,MAAM,cAAc,CAAA;AAsB5E;;;;GAIG;AACH,wBAAgB,oBAAoB,CAAC,MAAM,GAAE,aAAwB,GAAG,UAAU,CAUjF"}
|
|
@@ -1,58 +0,0 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* 过渡期的跨插件桥:把 dsh-later / dsh-gitea-dispatch 的摘要面接到 facet 登记面上。
|
|
3
|
-
*
|
|
4
|
-
* ⚠️ 本目录整体是**临时代管**。两个提供方按 `../facets.ts` 的协议自己注册之后
|
|
5
|
-
* (对应它们各自的 issue),`legacy/` 整个目录与 `package.json` 里的
|
|
6
|
-
* `dsh.client.external` 两条声明一并删除,本插件不再认识任何具体状态源。
|
|
7
|
-
*
|
|
8
|
-
* ## 为什么在这里、又为什么要"登记表"
|
|
9
|
-
*
|
|
10
|
-
* 两家的 store 都在自己的 client `apply` 里创建,而**插件 apply 的先后宿主不保证**:
|
|
11
|
-
* 本插件可能在对方 store 就绪之前就开始渲染。所以桥接层不能一次性抓 store,必须
|
|
12
|
-
* 订阅对方的"store 登记变化",并把 store 的迟到本身当作一次快照变化通知出去
|
|
13
|
-
* (`subscribe` 里同时挂两层)。这与 `cross-plugin-summary.ts` 里 `createSummaryRegistry`
|
|
14
|
-
* 解决的是一模一样的问题,只是这次藏在桥接层里,不污染协议。
|
|
15
|
-
*
|
|
16
|
-
* ## 为什么用 subscribe/getSnapshot 而不是调对方的 hook
|
|
17
|
-
*
|
|
18
|
-
* 见 `../facets.ts` 文件头:hook 数量必须逐次渲染恒定,而 facet 运行时可增删。桥接层
|
|
19
|
-
* 只要把对方的 store 面交出去,聚合侧就完全不需要知道背后有几个来源。
|
|
20
|
-
*
|
|
21
|
-
* @module dsh-group-status/client/legacy/bridge
|
|
22
|
-
*/
|
|
23
|
-
import { registry } from "../facets.js";
|
|
24
|
-
import { assembleLegacySources } from "./store-source.js";
|
|
25
|
-
import { registerLegacyFacets } from "./register-legacy-facets.js";
|
|
26
|
-
/**
|
|
27
|
-
* 读一个 provider 的 client 模块表行。
|
|
28
|
-
*
|
|
29
|
-
* 用**注入的** `require`(闭包工厂的参数)而不是 `globalThis.require`:宿主没有全局
|
|
30
|
-
* require(实测 `typeof globalThis.require === 'undefined'`),走全局会静默拿到
|
|
31
|
-
* undefined,于是整个跨插件集成"看起来装着、其实一直没工作"。
|
|
32
|
-
* 提供方未安装 / 未启用时模块表里没有这一行,`require` 抛错 → 当作缺席。
|
|
33
|
-
*/
|
|
34
|
-
function clientOf(specifier) {
|
|
35
|
-
try {
|
|
36
|
-
return require(specifier);
|
|
37
|
-
}
|
|
38
|
-
catch {
|
|
39
|
-
return undefined;
|
|
40
|
-
}
|
|
41
|
-
}
|
|
42
|
-
/**
|
|
43
|
-
* 安装过渡适配器。
|
|
44
|
-
*
|
|
45
|
-
* @param target - 登记面;缺省用生产单例,测试传入自建实例以隔离。
|
|
46
|
-
*/
|
|
47
|
-
export function installLegacyBridges(target = registry) {
|
|
48
|
-
const later = clientOf('dsh-later/client');
|
|
49
|
-
const dispatch = clientOf('dsh-gitea-dispatch/client');
|
|
50
|
-
// 缺席就省略键(exactOptionalPropertyTypes 下 undefined 不是"没有"的合法写法)。
|
|
51
|
-
const clients = {
|
|
52
|
-
...(later === undefined ? {} : { later }),
|
|
53
|
-
...(dispatch === undefined ? {} : { dispatch }),
|
|
54
|
-
};
|
|
55
|
-
const sources = assembleLegacySources(clients);
|
|
56
|
-
return registerLegacyFacets(sources, target);
|
|
57
|
-
}
|
|
58
|
-
//# sourceMappingURL=bridge.js.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"bridge.js","sourceRoot":"","sources":["../../../../src/client/legacy/bridge.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,OAAO,EAAE,QAAQ,EAAuC,MAAM,cAAc,CAAA;AAC5E,OAAO,EAAE,qBAAqB,EAA8B,MAAM,mBAAmB,CAAA;AACrF,OAAO,EAAE,oBAAoB,EAAE,MAAM,6BAA8B,CAAA;AAInE;;;;;;;GAOG;AACH,SAAS,QAAQ,CAAI,SAAiB;IACpC,IAAI,CAAC;QACH,OAAO,OAAO,CAAC,SAAS,CAAkB,CAAA;IAC5C,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,SAAS,CAAA;IAClB,CAAC;AACH,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,oBAAoB,CAAC,SAAwB,QAAQ;IACnE,MAAM,KAAK,GAAG,QAAQ,CAAiC,kBAAkB,CAAC,CAAA;IAC1E,MAAM,QAAQ,GAAG,QAAQ,CAAoC,2BAA2B,CAAC,CAAA;IACzF,8DAA8D;IAC9D,MAAM,OAAO,GAA0B;QACrC,GAAG,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,CAAC;QACzC,GAAG,CAAC,QAAQ,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,QAAQ,EAAE,CAAC;KAChD,CAAA;IACD,MAAM,OAAO,GAAG,qBAAqB,CAAC,OAAO,CAAC,CAAA;IAC9C,OAAO,oBAAoB,CAAC,OAAO,EAAE,MAAM,CAAC,CAAA;AAC9C,CAAC"}
|
|
@@ -1,14 +0,0 @@
|
|
|
1
|
-
import { type FacetRegistry, type Unregister } from '../facets.ts';
|
|
2
|
-
import type { LegacyFacetSources } from './store-source.ts';
|
|
3
|
-
/**
|
|
4
|
-
* 登记本插件目前**代管**的状态源。
|
|
5
|
-
*
|
|
6
|
-
* 两个 facet 都显式声明 `origin: 'legacy'`,所以状态所有者一旦自己注册同名 facet,
|
|
7
|
-
* 适配器就让位({@link FACET_ORIGIN_RANK}),不会重复计数。
|
|
8
|
-
*
|
|
9
|
-
* @returns 一次性注销函数(挂到 `ctx.effect` 的清理上)。
|
|
10
|
-
*/
|
|
11
|
-
export declare function registerLegacyFacets(sources: LegacyFacetSources, target?: FacetRegistry): Unregister;
|
|
12
|
-
/** 本插件目前代管了哪些状态源(诊断与测试用)。 */
|
|
13
|
-
export declare const LEGACY_FACET_IDS: readonly string[];
|
|
14
|
-
//# sourceMappingURL=register-legacy-facets.d.ts.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"register-legacy-facets.d.ts","sourceRoot":"","sources":["../../../../src/client/legacy/register-legacy-facets.tsx"],"names":[],"mappings":"AAYA,OAAO,EAA2C,KAAK,aAAa,EAAyB,KAAK,UAAU,EAAE,MAAM,cAAc,CAAA;AAGlI,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,mBAAmB,CAAA;AAkB3D;;;;;;;GAOG;AACH,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,kBAAkB,EAAE,MAAM,GAAE,aAA+B,GAAG,UAAU,CAwCrH;AAUD,6BAA6B;AAC7B,eAAO,MAAM,gBAAgB,EAAE,SAAS,MAAM,EAAiD,CAAA"}
|
|
@@ -1,77 +0,0 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* 过渡期:把内置适配器登记进 facet 注册面,并交出它们各自的图标。
|
|
3
|
-
*
|
|
4
|
-
* ⚠️ 本文件与整个 `legacy/` 目录都是**临时代管**:状态所有者(dsh-later、
|
|
5
|
-
* dsh-gitea-dispatch)按 `../facets.ts` 的协议自己注册之后,这里连同两个适配器一起
|
|
6
|
-
* 删除。图标之所以留在这一层而不是放回 `rows/GroupBadge.tsx`:「这个状态长什么样」
|
|
7
|
-
* 是状态所有者的知识,本插件只管把它放进徽标的排格里。
|
|
8
|
-
*
|
|
9
|
-
* @module dsh-group-status/client/legacy/register-legacy-facets
|
|
10
|
-
*/
|
|
11
|
-
import { createElement } from 'react';
|
|
12
|
-
import { IconClockOutlineRegular, IconListPenOutlineRegular } from '@deepseek-ai/dsh-client-ui-primitives';
|
|
13
|
-
import { registerGroupStatusFacet } from "../facets.js";
|
|
14
|
-
import { registry as defaultRegistry } from "../facets.js";
|
|
15
|
-
import { createScheduleFacet, SCHEDULE_FACET_ID } from "./schedule.js";
|
|
16
|
-
import { createWaitingReviewFacet, WAITING_REVIEW_FACET_ID, } from "./waiting-review.js";
|
|
17
|
-
/** 语义色档 → 宿主色令牌(与改造前的取色逐档一致)。 */
|
|
18
|
-
const TONE_COLOR = {
|
|
19
|
-
info: '#8b5cf6',
|
|
20
|
-
warn: 'var(--dsw-alias-state-warn-secondary)',
|
|
21
|
-
error: 'var(--dsw-alias-state-error-primary)',
|
|
22
|
-
};
|
|
23
|
-
/** 带色的一小段 inline-flex,尺寸与其余徽标图标一致。 */
|
|
24
|
-
function glyph(color, icon) {
|
|
25
|
-
return createElement('span', { style: { color, display: 'inline-flex', alignItems: 'center' } }, icon);
|
|
26
|
-
}
|
|
27
|
-
/**
|
|
28
|
-
* 登记本插件目前**代管**的状态源。
|
|
29
|
-
*
|
|
30
|
-
* 两个 facet 都显式声明 `origin: 'legacy'`,所以状态所有者一旦自己注册同名 facet,
|
|
31
|
-
* 适配器就让位({@link FACET_ORIGIN_RANK}),不会重复计数。
|
|
32
|
-
*
|
|
33
|
-
* @returns 一次性注销函数(挂到 `ctx.effect` 的清理上)。
|
|
34
|
-
*/
|
|
35
|
-
export function registerLegacyFacets(sources, target = defaultRegistry) {
|
|
36
|
-
const disposers = [];
|
|
37
|
-
if (sources.schedule !== undefined) {
|
|
38
|
-
const facet = {
|
|
39
|
-
...createScheduleFacet(sources.schedule),
|
|
40
|
-
// 紫色与 dsh-later 自己的定时徽标同源(浅深底对比均 >=3:1);
|
|
41
|
-
// urgent / overdue 走宿主 warn / error 语义令牌。
|
|
42
|
-
renderIcon: (fold) => glyph(fold.tone === 'error' ? TONE_COLOR.error : fold.tone === 'warn' ? TONE_COLOR.warn : TONE_COLOR.info, createElement(IconClockOutlineRegular, { size: 14 })),
|
|
43
|
-
};
|
|
44
|
-
disposers.push(target === defaultRegistry
|
|
45
|
-
? registerGroupStatusFacet(facet)
|
|
46
|
-
: registerInto(target, facet));
|
|
47
|
-
}
|
|
48
|
-
if (sources.waiting !== undefined) {
|
|
49
|
-
const facet = {
|
|
50
|
-
...createWaitingReviewFacet(sources.waiting),
|
|
51
|
-
// #23:这枚「列表笔」是**过时刻意保留的兜底形状,不是当前形状**。dsh-gitea-dispatch
|
|
52
|
-
// 自其 #56/#60 起交出自绘的沙漏(跟随 waitingIconStyle 四档),本文件按
|
|
53
|
-
// FACET_ORIGIN_RANK 让位给它(provider 恒胜 legacy)。只有 provider 缺席
|
|
54
|
-
//(未安装 / 版本早于 #47)或登记失败时才会现形——那些路径下形状与行内不一致是
|
|
55
|
-
// **有意接受的**,好过「等待评审彻底不进徽标」。别把它当成 bug 改回沙漏。
|
|
56
|
-
// 与定时任务仍用不同图标:两者同属"在等"的语义,只靠颜色区分对色盲用户不可用。
|
|
57
|
-
renderIcon: (fold) => glyph(fold.tone === 'error' ? TONE_COLOR.error : TONE_COLOR.warn, createElement(IconListPenOutlineRegular, { size: 14 })),
|
|
58
|
-
};
|
|
59
|
-
disposers.push(target === defaultRegistry
|
|
60
|
-
? registerGroupStatusFacet(facet)
|
|
61
|
-
: registerInto(target, facet));
|
|
62
|
-
}
|
|
63
|
-
return () => {
|
|
64
|
-
for (const dispose of disposers)
|
|
65
|
-
dispose();
|
|
66
|
-
};
|
|
67
|
-
}
|
|
68
|
-
/** 对给定登记面注册一个 facet(与单例路径同一套校验/拒绝语义)。 */
|
|
69
|
-
function registerInto(target, facet) {
|
|
70
|
-
const result = target.register(facet);
|
|
71
|
-
return result.ok ? () => {
|
|
72
|
-
target.remove(result.id, facet);
|
|
73
|
-
} : () => undefined;
|
|
74
|
-
}
|
|
75
|
-
/** 本插件目前代管了哪些状态源(诊断与测试用)。 */
|
|
76
|
-
export const LEGACY_FACET_IDS = [SCHEDULE_FACET_ID, WAITING_REVIEW_FACET_ID];
|
|
77
|
-
//# sourceMappingURL=register-legacy-facets.js.map
|