dsh-wsl-tool 1.10.1 → 1.10.2

package/lib/client.js

@@ -163,6 +163,25 @@ window.__ModuleLoader__.load({
       revision: undefined,
     }
 
+    /**
+     * No scope yet — the Host has not listed this namespace, or its `describe()`
+     * round trip is still in flight.
+     *
+     * This is deliberately NOT the unavailable snapshot: a panel that reads "this
+     * DSH does not provide the plugin's settings scope" while it is merely still
+     * waiting sends whoever is debugging it after the wrong thing (measured: it
+     * said exactly that for a namespace the Host was already serving, because the
+     * form had been taken before the round trip settled).
+     */
+    const PENDING_SNAPSHOT = {
+      status: 'loading',
+      value: undefined,
+      base: undefined,
+      user: undefined,
+      writable: false,
+      revision: undefined,
+    }
+
     // ---------------------------------------------------------------- helpers
 
     /** Read one path out of a possibly absent object, never throwing. */
@@ -218,7 +237,7 @@ window.__ModuleLoader__.load({
 
       const read = () => {
         if (scope === undefined || scope === null || typeof scope.getSnapshot !== 'function') {
-          return UNAVAILABLE_SNAPSHOT
+          return PENDING_SNAPSHOT
         }
         try {
           const snapshot = scope.getSnapshot()
@@ -231,8 +250,15 @@ window.__ModuleLoader__.load({
 
       return {
         /** Whether the `configForms` service was there at all. A service this DSH
-         *  does not ship reads differently from a row it does not serve. */
+         *  does not ship reads differently from a row it does not serve — and both
+         *  read differently from a namespace that simply has not been listed yet. */
         hasService: () => served,
+        /** Record that the service exists, before any scope is available. Without
+         *  this, a namespace that has not been served yet reads as "this DSH has no
+         *  configuration forms", which is a different (and wrong) diagnosis. */
+        noteService: () => {
+          served = true
+        },
         /** Bind the scope once the service appears. */
         attach: (next) => {
           if (next === undefined || next === null) return
@@ -542,7 +568,8 @@ window.__ModuleLoader__.load({
           ),
         )
       } else if (snapshot.status === 'loading') {
-        children.push(React.createElement('p', { key: 'note-loading', style: NOTE_STYLE }, '正在读取配置…'))
+        children.push(React.createElement('p', { key: 'note-loading', style: NOTE_STYLE },
+          '正在等待 Host 提供该插件的配置作用域（' + CONFIG_ROW_ID + '）…'))
       } else if (snapshot.status !== 'ready') {
         children.push(
           React.createElement('p', { key: 'note-unavailable', style: NOTE_STYLE }, '此 DSH 未提供该插件的配置作用域'),
@@ -632,18 +659,51 @@ window.__ModuleLoader__.load({
       try {
         if (typeof ctx.inject === 'function') {
           ctx.inject(['configForms'], (inner) => {
-            let scope
+            const configForms = inner.configForms
+            if (configForms === undefined || configForms === null) return
+            // The service is here; whether it lists our namespace is a separate
+            // question that `whileServed` answers below.
+            model.noteService()
+            /**
+             * Take the form once the Host actually lists the namespace.
+             *
+             * A form fetched before the `describe()` round trip settles is born
+             * with its persistence already fixed to "not host" and never upgrades
+             * — it stays `unavailable` forever. That is exactly how this panel
+             * lost every switch while the tools kept working, so the namespace is
+             * awaited through the platform's own gate instead of being requested
+             * eagerly. The shipped settings pages use this same call.
+             */
+            const attachWhenServed = () => {
+              if (typeof configForms.whileServed !== 'function') {
+                // Older host face: no gate to wait on, so take whatever it gives
+                // and let the model report `unavailable` honestly.
+                attach(configForms.get(CONFIG_ROW_ID))
+                return () => model.detach()
+              }
+              return configForms.whileServed([CONFIG_ROW_ID], () => {
+                attach(configForms.get(CONFIG_ROW_ID))
+                return () => model.detach()
+              })
+            }
+            const attach = (scope) => {
+              try {
+                model.attach(scope)
+              } catch (error) {
+                console.error('dsh-wsl-tool: reading the "' + CONFIG_ROW_ID + '" configuration scope failed', error)
+              }
+            }
+            let stop
             try {
-              scope = inner.configForms.get(CONFIG_ROW_ID)
+              stop = attachWhenServed()
             } catch (error) {
               console.error('dsh-wsl-tool: this DSH serves no "' + CONFIG_ROW_ID + '" configuration row', error)
               return
             }
-            model.attach(scope)
             // The subscription lives exactly as long as this fiber: `effect` runs
             // the returned disposer on unload or recomposition.
             if (typeof inner.effect === 'function') {
-              inner.effect(() => () => model.detach(), 'dsh-wsl-tool: configuration scope')
+              inner.effect(() => stop, 'dsh-wsl-tool: configuration scope')
             }
           })
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-wsl-tool",
-  "version": "1.10.1",
+  "version": "1.10.2",
   "description": "Run Linux commands from Windows through WSL, essentially matching a native Linux DSH for command execution: background jobs, stdin, path translation, a destructive-command guard and a WSL capability report. A left-sidebar panel switches each capability on or off, each with a one-line explanation, and an opt-in patch gives the desktop app's sidebar terminal a WSL shell. WSL calls run below the DSH sandbox, and a project on a Windows drive keeps Windows filesystem semantics.",
   "type": "module",
   "main": "index.js",