@linkdesk/plugin-docs 0.1.33 → 0.1.34
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/docs/03-contributes-spec.md +40 -2
- package/docs/06-plugin-json-spec.md +2 -2
- package/docs/10-building-a-settings-plugin.md +17 -1
- package/docs/zh/03-/346/217/222/344/273/266contributes/350/247/204/350/214/203.md +40 -2
- package/docs/zh/06-plugin.json/350/247/204/350/214/203.md +2 -2
- package/docs/zh/10-/345/246/202/344/275/225/351/200/240/344/270/200/344/270/252/350/256/276/347/275/256/346/217/222/344/273/266.md +17 -1
- package/docs/zh/plugin.schema.json +5 -2
- package/package.json +1 -1
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
| `titleBar` | ✅ | top bar left/right slot buttons | MenuRegistry |
|
|
34
34
|
| `viewsContainers` | ✅ | declare sidebar/panel containers | ViewContainerService |
|
|
35
35
|
| `views` | ✅ | register views in a container — any plugin can register in any container | ViewContainerService |
|
|
36
|
-
| `floatingPanel` | ✅ | declare that a view can be shown in a shell-internal floating panel (type B) — `viewId` references an already-registered view; without the declaration there is no "Open in Floating Panel" context menu item | declaration addressing → FloatingPanelService |
|
|
36
|
+
| `floatingPanel` | ✅ | declare that a view can be shown in a shell-internal floating panel (type B) — `viewId` references an already-registered view; without the declaration there is no "Open in Floating Panel" context menu item; optional `defaultForm`/`formKey` fix or offer the **first-open form** (§3.15) | declaration addressing → FloatingPanelService |
|
|
37
37
|
| `i18n` | ✅ | plugin-bundled translation files | i18nResources (i18next namespace) |
|
|
38
38
|
|
|
39
39
|
### Main-process consumers (2)
|
|
@@ -733,6 +733,8 @@ useEffect(() => {
|
|
|
733
733
|
| Field | Required | Description |
|
|
734
734
|
|------|:--:|------|
|
|
735
735
|
| `viewId` | ✅ | **a view ID already registered in contributes.views** — declaration addressing resolves the plugin/renderPath/title |
|
|
736
|
+
| `defaultForm` | ❌ | the form used the **first time** the view is opened, fixed by the author (the user gets no entry point): `"floatingPanel"` (floating panel) \| `"tab"` (tab) |
|
|
737
|
+
| `formKey` | ❌ | the **first-open** form is **left to the user**: a configuration key name (you declare that key in `contributes.configuration`; its `default` is your default form) |
|
|
736
738
|
|
|
737
739
|
**Declaring is consuming — four things appear automatically:**
|
|
738
740
|
|
|
@@ -743,7 +745,43 @@ useEffect(() => {
|
|
|
743
745
|
| `linkdesk.panel.revealFloating(viewId)` opens the panel programmatically | panel identity toggle semantics — no panel → open; same view → close; another panel → replace |
|
|
744
746
|
| Uninstalling the declaring plugin → the menu item disappears + revealFloating no-ops without crashing | the declaration unloads with the plugin lifecycle |
|
|
745
747
|
|
|
746
|
-
|
|
748
|
+
#### Configurable first-open form (`defaultForm` / `formKey`) — authors who just want the panel to pop out add nothing
|
|
749
|
+
|
|
750
|
+
**Division of labour: the plugin only declares which form it wants; the shell decides and executes** — the plugin has zero execution power and the shell has zero plugin knowledge (the shell hard-codes no plugin ID, so any future declarer works without shell changes).
|
|
751
|
+
|
|
752
|
+
| What the author wants | How to write it | What the user sees in the Settings editor |
|
|
753
|
+
|:--|:--|:--|
|
|
754
|
+
| Fix the form, no user override | `"defaultForm": "tab"` | Nothing (no Settings item appears at all) |
|
|
755
|
+
| Let the user choose | `"formKey": "<plugin-id>.openForm"` plus declaring that key yourself in `contributes.configuration` | The control for that key (toggle/dropdown, rendered from your `type`) |
|
|
756
|
+
|
|
757
|
+
```json
|
|
758
|
+
{
|
|
759
|
+
"contributes": {
|
|
760
|
+
"floatingPanel": { "viewId": "settings", "formKey": "settings.openForm" },
|
|
761
|
+
"configuration": {
|
|
762
|
+
"title": "Settings plugin",
|
|
763
|
+
"properties": {
|
|
764
|
+
"settings.openForm": {
|
|
765
|
+
"type": "string",
|
|
766
|
+
"enum": ["floatingPanel", "tab"],
|
|
767
|
+
"default": "floatingPanel",
|
|
768
|
+
"description": "Form when opening Settings — floatingPanel / tab"
|
|
769
|
+
}
|
|
770
|
+
}
|
|
771
|
+
}
|
|
772
|
+
}
|
|
773
|
+
}
|
|
774
|
+
```
|
|
775
|
+
|
|
776
|
+
**The shell's decision chain** (first match wins; executed by "first open" entry points — today that is `core.openSettings`):
|
|
777
|
+
|
|
778
|
+
1. `formKey` is present and that key **is registered** → read its value: `"floatingPanel"` / `"tab"` is used as-is (**the value *is* the form — no mapping layer**);
|
|
779
|
+
2. otherwise `defaultForm` (only legal values are accepted);
|
|
780
|
+
3. neither → **previous behaviour** (a declaring plugin opens as a floating panel — today's settings default).
|
|
781
|
+
|
|
782
|
+
**Four boundaries**: ① it only governs the **first open** — an existing tab is still focused and an already-open panel still toggles shut; changing the form afterwards keeps using the two old paths ("Open in main window" / "Open in Floating Panel"); ② `formKey` and `defaultForm` are **mutually exclusive** (both declared ⇒ schema validation fails — one form from two sources); ③ a typo'd `formKey` / a key that was never registered ⇒ falls back to `defaultForm` (neither = previous behaviour) plus one warning — it **never fails silently**; ④ declaring `"defaultForm": "tab"` on a plugin with no tab form (`appearsIn.tabBar` + `entry`) falls back to the floating panel rather than silently doing nothing.
|
|
783
|
+
|
|
784
|
+
**The first declarer = settings** (`core.openSettings`, Ctrl+, opens the panel, and `settings.openForm` lets the user change it inside the "Settings plugin" group); **the second declarer, used as a validation vehicle = the `floating-panel-demo` test plugin** (a tab-style view; end-to-end validation of replacement + the right-click return path + unload no-op).
|
|
747
785
|
|
|
748
786
|
---
|
|
749
787
|
|
|
@@ -114,7 +114,7 @@ The `entry` field → the loader automatically recognizes this as a view plugin.
|
|
|
114
114
|
| `contributes.themes` | theme | registered into ThemeRegistry → theme browser |
|
|
115
115
|
| `contributes.languages` | language | registered into LanguageRegistry |
|
|
116
116
|
| `contributes.fileAssociations` | — | registered into FileAssociationService → double-clicking a file opens it automatically |
|
|
117
|
-
| `contributes.floatingPanel` | — | Declares that the view can be displayed in a floating panel inside the shell — viewId references an already-registered view; without the declaration there is no "Open in Floating Panel" context-menu item |
|
|
117
|
+
| `contributes.floatingPanel` | — | Declares that the view can be displayed in a floating panel inside the shell — viewId references an already-registered view; without the declaration there is no "Open in Floating Panel" context-menu item; optional `defaultForm`/`formKey` fix or offer the **first-open form** |
|
|
118
118
|
|
|
119
119
|
**A plugin can declare several contributions at once.** A view plugin, for example, can have `entry` + `sidebar` + `statusBar` + `contributes.configuration` + `contributes.commands` — each is registered independently and does not affect the others.
|
|
120
120
|
|
|
@@ -329,7 +329,7 @@ Plugin-level activation ordering — declares which plugins must be activated be
|
|
|
329
329
|
|
|
330
330
|
- **③ Switch entry point = a role group on the settings page (appearing dynamically)**: when the settings UI opens it enumerates `listRoles()` → for every **non-settings-plugin role** it calls `list(role)` → **a group is created only when there are ≥2 candidates** (a single candidate makes switching meaningless). Group shape = the switch button on top (listing every candidate for that role, the active one highlighted) + the active set's own configuration below; it reuses a group of the same name where possible (finding the active candidate's own configuration group by pluginId), and only creates a new one otherwise; if the active set has no settings, it shows an empty state. Switching = `setActive` → refetch data → the configuration follows the active set. Switching your settings plugin's **own role** (settings) = the button in the generic area at the top (see `10-building-a-settings-plugin.md`).
|
|
331
331
|
- **④ Icon bar slot occupancy**: for plugins that declare `factoryRole` (form 2), the icon bar **renders only the active set's icon** and hides inactive ones — "swap the official one out for yours"; form 1 plugins that do not declare it still all show up side by side as before.
|
|
332
|
-
- **⑤ Routing seam**: opening settings (`Ctrl+,` / the gear) = `factorySlots.getActive("settings")` → if a tab is already open, focus it /
|
|
332
|
+
- **⑤ Routing seam**: opening settings (`Ctrl+,` / the gear) = `factorySlots.getActive("settings")` → if a tab is already open, focus it / **the first-open form comes from the declaration** (`formKey` value → `defaultForm` → previous behaviour): `tab` → open a tab; `floatingPanel` → the floating panel (the payload carries pluginId for composite addressing); with no `floatingPanel` declaration this entry point does nothing (previous behaviour). After switching the active set, all subsequent opens go through the new set, consistently on both ends. **The first-open form only governs the first open** — converting between the panel and a tab afterwards keeps using the old paths (criteria and boundaries → `03-contributes-spec.md` §3.15).
|
|
333
333
|
- **⑥ Switching sets on the plugin side** (the switch button's click, zero shell changes): `setActive` → tab form = close this set's tab → open the target set (singleton dedupe focuses it if it already exists); floating panel form = `panel.revealFloating(viewId, pluginId?)` **replacing the panel content in place with composite addressing** (no leftover tab popping up behind; if the target set declares no floatingPanel → fall back to opening a tab). Deleting any set → `onPluginLifecycleChange` → refetch → the button disappears on its own.
|
|
334
334
|
|
|
335
335
|
**Two-scenario example (official + third-party plugin marketplace):**
|
|
@@ -36,13 +36,29 @@ Follow the official settings plugin (= the `plugin.json` in **the settings plugi
|
|
|
36
36
|
{ "id": "settings", "title": "Settings", "render": "src/views/SettingsView.tsx", "order": 0 }
|
|
37
37
|
]
|
|
38
38
|
},
|
|
39
|
-
"floatingPanel": { "viewId": "settings" } // ③ floating panel form (optional)
|
|
39
|
+
"floatingPanel": { "viewId": "settings", "formKey": "settings.openForm" } // ③ floating panel form (optional) — formKey hands the first-open form to the user
|
|
40
40
|
}
|
|
41
41
|
}
|
|
42
42
|
```
|
|
43
43
|
|
|
44
44
|
All three key declarations are required: **`factoryRole: "settings"`** (puts you in the shared-area candidate list) + **`contributes.views`** (the actual render component) + **`floatingPanel`** (the `Ctrl+,` fallback form).
|
|
45
45
|
|
|
46
|
+
**The first-open form is configurable (optional; write nothing and it opens as a floating panel)**: to let the user choose (floating panel / tab), add `"formKey": "<plugin-id>.openForm"` to `floatingPanel` and declare that key yourself — the key's `default` is your default form:
|
|
47
|
+
|
|
48
|
+
```json
|
|
49
|
+
"configuration": {
|
|
50
|
+
"title": "Settings plugin",
|
|
51
|
+
"properties": {
|
|
52
|
+
"settings.openForm": {
|
|
53
|
+
"type": "string", "enum": ["floatingPanel", "tab"], "default": "floatingPanel",
|
|
54
|
+
"description": "Form when opening Settings — floatingPanel / tab"
|
|
55
|
+
}
|
|
56
|
+
}
|
|
57
|
+
}
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
To fix the form with no user override, write `"defaultForm": "tab"` instead (no configuration key ⇒ no Settings item appears at all). The two are **mutually exclusive** (declaring both fails schema validation); the decision chain, the boundaries and the "the shell decides, the plugin only declares" split → [`03-contributes-spec.md` §3.15](03-contributes-spec.md).
|
|
61
|
+
|
|
46
62
|
## Data API shape — everything goes through `window.linkdesk.*`
|
|
47
63
|
|
|
48
64
|
Settings plugins are **forbidden from `import @src/core/...`** (the plugin communication iron rule + ESLint `noCoreImportInPlugin`). All data is in the public API:
|
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
| `titleBar` | ✅ | 顶栏左右槽位按钮 | MenuRegistry |
|
|
34
34
|
| `viewsContainers` | ✅ | 声明侧栏/面板容器 | ViewContainerService |
|
|
35
35
|
| `views` | ✅ | 往容器注册视图——任何插件可往任意容器注册 | ViewContainerService |
|
|
36
|
-
| `floatingPanel` | ✅ | 声明某视图可在壳内悬浮面板显示(类型 B)——viewId
|
|
36
|
+
| `floatingPanel` | ✅ | 声明某视图可在壳内悬浮面板显示(类型 B)——viewId 引用已注册视图;未声明则无「在悬浮面板中打开」右键;可选 `defaultForm`/`formKey` 定/选**首开形态**(§3.15) | 声明寻址 → FloatingPanelService |
|
|
37
37
|
| `i18n` | ✅ | 插件自带翻译文件 | i18nResources(i18next 命名空间) |
|
|
38
38
|
|
|
39
39
|
### 主进程消费(2 个)
|
|
@@ -733,6 +733,8 @@ useEffect(() => {
|
|
|
733
733
|
| 字段 | 必需 | 说明 |
|
|
734
734
|
|------|:--:|------|
|
|
735
735
|
| `viewId` | ✅ | **contributes.views 中已注册的视图 ID**——声明寻址解析出插件/renderPath/title |
|
|
736
|
+
| `defaultForm` | ❌ | **首次打开**用哪种形态,作者定死(用户没入口):`"floatingPanel"`(悬浮面板)\| `"tab"`(标签页) |
|
|
737
|
+
| `formKey` | ❌ | **首次打开**形态**交给用户选**:填一个配置键名(键由你在 `contributes.configuration` 里声明,键的 `default` 即作者默认形态) |
|
|
736
738
|
|
|
737
739
|
**声明即消费,四件事自动出现:**
|
|
738
740
|
|
|
@@ -743,7 +745,43 @@ useEffect(() => {
|
|
|
743
745
|
| `linkdesk.panel.revealFloating(viewId)` 可编程弹面板 | 面板身份开关键——无面板→开;同视图→关;他面板→替换 |
|
|
744
746
|
| 卸载声明插件 → 右键条目消失 + revealFloating no-op 不崩 | 声明随插件生命周期卸载 |
|
|
745
747
|
|
|
746
|
-
|
|
748
|
+
#### 首开形态可配(`defaultForm` / `formKey`)——只想要面板能弹出来的作者一个字都不用加
|
|
749
|
+
|
|
750
|
+
**分工:插件只声明想要哪种,壳决定并执行**——插件零执行权、壳零插件知识(壳侧不认任何插件 ID,换一只声明者自动生效,不必改壳)。
|
|
751
|
+
|
|
752
|
+
| 作者想要 | 写法 | 用户在设置页的入口 |
|
|
753
|
+
|:--|:--|:--|
|
|
754
|
+
| 定死形态,不给用户改 | `"defaultForm": "tab"` | 无(设置页不出现任何项) |
|
|
755
|
+
| 让用户自己选 | `"formKey": "<插件id>.openForm"` + 自己在 `contributes.configuration` 里声明这个键 | 该键的控件(布尔/下拉按你的 `type` 渲染) |
|
|
756
|
+
|
|
757
|
+
```json
|
|
758
|
+
{
|
|
759
|
+
"contributes": {
|
|
760
|
+
"floatingPanel": { "viewId": "settings", "formKey": "settings.openForm" },
|
|
761
|
+
"configuration": {
|
|
762
|
+
"title": "设置插件",
|
|
763
|
+
"properties": {
|
|
764
|
+
"settings.openForm": {
|
|
765
|
+
"type": "string",
|
|
766
|
+
"enum": ["floatingPanel", "tab"],
|
|
767
|
+
"default": "floatingPanel",
|
|
768
|
+
"description": "打开设置时的形态——floatingPanel 悬浮面板 / tab 标签页"
|
|
769
|
+
}
|
|
770
|
+
}
|
|
771
|
+
}
|
|
772
|
+
}
|
|
773
|
+
}
|
|
774
|
+
```
|
|
775
|
+
|
|
776
|
+
**壳的判定链**(第一命中即定;由「第一次打开」这一类入口执行——今天 = `core.openSettings`):
|
|
777
|
+
|
|
778
|
+
1. `formKey` 有、且那个键**已注册** → 读它的值:`"floatingPanel"` / `"tab"` 直接用(**值即形态,无映射层**);
|
|
779
|
+
2. 否则看 `defaultForm`(合法值才认);
|
|
780
|
+
3. 都没有 → **原行为**(声明了面板即面板——今天设置插件的默认)。
|
|
781
|
+
|
|
782
|
+
**四条边界**:① 只管**第一次打开**——已有标签页仍聚焦、面板开着再点仍按开关键关掉,打开之后想换形态照旧走「在主窗口中打开」/「在悬浮面板中打开」两条老路;② `formKey` 与 `defaultForm` **互斥**(同时写 ⇒ schema 校验红:一个形态两个来源);③ `formKey` 写错字 / 没注册那个键 ⇒ 降级 `defaultForm`(都没有 = 原行为)+ 出声一条 warn——**不静默失效**;④ 声明 `"defaultForm": "tab"` 但插件没有标签页形态(`appearsIn.tabBar` + `entry`)⇒ 落回悬浮面板,不静默无动作。
|
|
783
|
+
|
|
784
|
+
**首批声明者 = settings**(`core.openSettings` Ctrl+, 弹面板,`settings.openForm` 在「设置插件」组里让用户改);**第二声明者验证载体 = `floating-panel-demo`** 测试插件(标签页型视图,端到端验证替换 + 右键回程 + 卸载 no-op)。
|
|
747
785
|
|
|
748
786
|
---
|
|
749
787
|
|
|
@@ -114,7 +114,7 @@ my-plugin/
|
|
|
114
114
|
| `contributes.themes` | theme | 注册到 ThemeRegistry → 主题浏览器 |
|
|
115
115
|
| `contributes.languages` | language | 注册到 LanguageRegistry |
|
|
116
116
|
| `contributes.fileAssociations` | — | 注册到 FileAssociationService → 双击文件自动打开 |
|
|
117
|
-
| `contributes.floatingPanel` | — | 声明视图可在壳内悬浮面板显示——viewId
|
|
117
|
+
| `contributes.floatingPanel` | — | 声明视图可在壳内悬浮面板显示——viewId 引用已注册视图;未声明则无「在悬浮面板中打开」右键;可选 `defaultForm`/`formKey` 定/选**首开形态** |
|
|
118
118
|
|
|
119
119
|
**插件可同时声明多种贡献。** 比如一个视图插件可以有 `entry` + `sidebar` + `statusBar` + `contributes.configuration` + `contributes.commands`——全部独立注册,互不影响。
|
|
120
120
|
|
|
@@ -329,7 +329,7 @@ my-plugin/
|
|
|
329
329
|
|
|
330
330
|
- **③ 切换入口 = 设置页角色分组(动态出现)**:设置 UI 打开时枚举 `listRoles()` → 对每个**非设置插件角色** `list(role)` → **候选 ≥2 才建组**(单候选无切换意义)。组形态 = 切换按钮在顶(列出该角色全部候选,激活高亮)+ 激活套自己的配置在下方;复用同名组优先(按 pluginId 找激活候选自己的配置组)、没有才新建;激活套无配置项 → 空状态。切换 = `setActive` → 重拉数据 → 配置随激活套换。你的设置插件**自身角色**(settings)的切换 = 顶部通用区按钮(见 `10-如何造一个设置插件.md`)。
|
|
331
331
|
- **④ 图标栏占槽**:声明 `factoryRole` 的插件(形态二),图标栏**只渲染激活套图标**、非激活套隐藏——"把官方的剔除换成你的";不声明的形态一照旧全出并排。
|
|
332
|
-
- **⑤ 路由接缝**:打开设置(`Ctrl+,` / 齿轮)= `factorySlots.getActive("settings")` → 已开标签页聚焦 /
|
|
332
|
+
- **⑤ 路由接缝**:打开设置(`Ctrl+,` / 齿轮)= `factorySlots.getActive("settings")` → 已开标签页聚焦 / **按声明定首开形态**(`formKey` 键值 → `defaultForm` → 原行为):`tab` → 开标签页;`floatingPanel` → 悬浮面板(载荷带 pluginId 复合寻址);无 `floatingPanel` 声明 → 本入口不动(原行为)。切换激活套后,后续打开全走新套,两端一致。**首开形态只管「第一次打开」**——打开之后的面板↔标签页互转仍各走原路(判据与边界 → `03-插件contributes规范.md` §3.15)。
|
|
333
333
|
- **⑥ 全插件侧换套**(切换按钮点击,零壳改动):`setActive` → 标签页形态 = 关本套 tab → 开目标套(singleton 去重已存在则聚焦);悬浮面板形态 = `panel.revealFloating(viewId, pluginId?)` **原地复合替换**面板内容(不背后弹残留 tab;目标套无 floatingPanel 声明 → 退回开标签页)。删任意套 → `onPluginLifecycleChange` → 重拉 → 按钮自动消失。
|
|
334
334
|
|
|
335
335
|
**双场景示例(官方 + 第三方 插件市场):**
|
|
@@ -36,13 +36,29 @@
|
|
|
36
36
|
{ "id": "settings", "title": "设置", "render": "src/views/SettingsView.tsx", "order": 0 }
|
|
37
37
|
]
|
|
38
38
|
},
|
|
39
|
-
"floatingPanel": { "viewId": "settings" } // ③
|
|
39
|
+
"floatingPanel": { "viewId": "settings", "formKey": "settings.openForm" } // ③ 悬浮面板形态(可选)——formKey 把首开形态交给用户
|
|
40
40
|
}
|
|
41
41
|
}
|
|
42
42
|
```
|
|
43
43
|
|
|
44
44
|
三个关键声明缺一不可:**`factoryRole: "settings"`**(进通用区候选列表)+ **`contributes.views`**(真实渲染组件)+ **`floatingPanel`**(`Ctrl+,` 兜底形态)。
|
|
45
45
|
|
|
46
|
+
**首开形态可配(可选,一个字不写 = 打开即悬浮面板)**:想让用户自己选(悬浮面板 / 标签页),就给 `floatingPanel` 加 `"formKey": "<插件id>.openForm"` 并自己声明那个键——键的 `default` 即你的默认形态:
|
|
47
|
+
|
|
48
|
+
```json
|
|
49
|
+
"configuration": {
|
|
50
|
+
"title": "设置插件",
|
|
51
|
+
"properties": {
|
|
52
|
+
"settings.openForm": {
|
|
53
|
+
"type": "string", "enum": ["floatingPanel", "tab"], "default": "floatingPanel",
|
|
54
|
+
"description": "打开设置时的形态——floatingPanel 悬浮面板 / tab 标签页"
|
|
55
|
+
}
|
|
56
|
+
}
|
|
57
|
+
}
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
定死不让用户改则写 `"defaultForm": "tab"`(不给配置项,设置页就不出现任何项)。两者**互斥**(同时写 = schema 校验红);判定链、边界与「壳决定并执行、插件只声明」的分工 → [`03-插件contributes规范.md` §3.15](03-插件contributes规范.md)。
|
|
61
|
+
|
|
46
62
|
## 数据 API 形状——全走 `window.linkdesk.*`
|
|
47
63
|
|
|
48
64
|
设置插件**禁止 `import @src/core/...`**(插件通信铁律 + ESLint `noCoreImportInPlugin`)。数据全在公开 API:
|
|
@@ -620,9 +620,12 @@
|
|
|
620
620
|
"description": "Floating Panel declaration — declares that a view in contributes.views can be shown in a Floating Panel inside the shell. viewId must reference an already registered view: the declaration is resolved into pluginId/renderPath/title. Without it there is no 'Open in Floating Panel' context menu entry. The first declarer is settings (Ctrl+, opens the panel).",
|
|
621
621
|
"required": ["viewId"],
|
|
622
622
|
"properties": {
|
|
623
|
-
"viewId": { "type": "string", "description": "View ID — a view registered in contributes.views" }
|
|
623
|
+
"viewId": { "type": "string", "description": "View ID — a view registered in contributes.views" },
|
|
624
|
+
"defaultForm": { "enum": ["floatingPanel", "tab"], "description": "Form used the FIRST time this view is opened — 'floatingPanel' (Floating Panel inside the shell) or 'tab'. Author-fixed: the user gets no Settings entry. Omit to keep the previous behaviour (a declaring plugin opens as a Floating Panel). Mutually exclusive with formKey." },
|
|
625
|
+
"formKey": { "type": "string", "description": "Configuration key that lets the USER choose the first-open form. Must be declared in this same plugin's contributes.configuration: its default is the author's default form, and its value must be 'floatingPanel' or 'tab' (any other value falls back to the author-fixed form). Declaring it makes the item appear in the Settings editor. Mutually exclusive with defaultForm." }
|
|
624
626
|
},
|
|
625
|
-
"additionalProperties": false
|
|
627
|
+
"additionalProperties": false,
|
|
628
|
+
"not": { "required": ["defaultForm", "formKey"] }
|
|
626
629
|
},
|
|
627
630
|
"i18n": {
|
|
628
631
|
"type": "object",
|