@agentchatme/openclaw 0.6.3 → 0.6.4
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 +67 -0
- package/dist/index.cjs +1 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +2 -2
- package/dist/index.d.ts +2 -2
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/dist/{setup-entry-Cr6cKgzq.d.cts → setup-entry-BfMtQopR.d.cts} +12 -3
- package/dist/{setup-entry-Cr6cKgzq.d.ts → setup-entry-BfMtQopR.d.ts} +12 -3
- package/dist/setup-entry.cjs +1 -1
- package/dist/setup-entry.cjs.map +1 -1
- package/dist/setup-entry.d.cts +1 -1
- package/dist/setup-entry.d.ts +1 -1
- package/dist/setup-entry.js +1 -1
- package/dist/setup-entry.js.map +1 -1
- package/openclaw.plugin.json +1 -9
- package/package.json +1 -1
|
@@ -44,9 +44,18 @@ type AgentchatChannelConfig = z.infer<typeof agentchatChannelConfigSchema>;
|
|
|
44
44
|
/**
|
|
45
45
|
* Parse + validate config at plugin startup.
|
|
46
46
|
*
|
|
47
|
-
*
|
|
48
|
-
*
|
|
49
|
-
*
|
|
47
|
+
* Strict on `apiKey` and the four nested groups — `parseChannelConfig` is
|
|
48
|
+
* called only AFTER `resolveAgentchatAccount` has confirmed that the
|
|
49
|
+
* persisted config block is non-empty (see `channel.ts`), so an empty
|
|
50
|
+
* install-time config never reaches Zod. The runtime-time strictness here
|
|
51
|
+
* surfaces typos and out-of-range values fast. The OpenClaw install-time
|
|
52
|
+
* JSON Schema (emitted by `scripts/emit-manifest-schema.mjs`) is more
|
|
53
|
+
* permissive — see that script's post-process step for the rationale —
|
|
54
|
+
* so a freshly-installed plugin can pass install validation against an
|
|
55
|
+
* empty config block before the setup wizard fills in credentials.
|
|
56
|
+
*
|
|
57
|
+
* `AgentChatChannelError` wraps validation failures so the gateway can
|
|
58
|
+
* classify them (`terminal-user` — operator fix required).
|
|
50
59
|
*/
|
|
51
60
|
declare function parseChannelConfig(input: unknown): AgentchatChannelConfig;
|
|
52
61
|
|
|
@@ -44,9 +44,18 @@ type AgentchatChannelConfig = z.infer<typeof agentchatChannelConfigSchema>;
|
|
|
44
44
|
/**
|
|
45
45
|
* Parse + validate config at plugin startup.
|
|
46
46
|
*
|
|
47
|
-
*
|
|
48
|
-
*
|
|
49
|
-
*
|
|
47
|
+
* Strict on `apiKey` and the four nested groups — `parseChannelConfig` is
|
|
48
|
+
* called only AFTER `resolveAgentchatAccount` has confirmed that the
|
|
49
|
+
* persisted config block is non-empty (see `channel.ts`), so an empty
|
|
50
|
+
* install-time config never reaches Zod. The runtime-time strictness here
|
|
51
|
+
* surfaces typos and out-of-range values fast. The OpenClaw install-time
|
|
52
|
+
* JSON Schema (emitted by `scripts/emit-manifest-schema.mjs`) is more
|
|
53
|
+
* permissive — see that script's post-process step for the rationale —
|
|
54
|
+
* so a freshly-installed plugin can pass install validation against an
|
|
55
|
+
* empty config block before the setup wizard fills in credentials.
|
|
56
|
+
*
|
|
57
|
+
* `AgentChatChannelError` wraps validation failures so the gateway can
|
|
58
|
+
* classify them (`terminal-user` — operator fix required).
|
|
50
59
|
*/
|
|
51
60
|
declare function parseChannelConfig(input: unknown): AgentchatChannelConfig;
|
|
52
61
|
|