fix(discord): align DiscordAccountConfig.token type with SecretInput#32490
Merged
joshavant merged 3 commits intoopenclaw:mainfrom Mar 3, 2026
Merged
Conversation
Contributor
Greptile SummaryThis PR fixes a type-layer inconsistency by updating
Confidence Score: 5/5
Last reviewed commit: 393681a |
393681a to
c21aaba
Compare
joshavant
added a commit
to scoootscooob/openclaw
that referenced
this pull request
Mar 3, 2026
The Zod schema (SecretInputSchema) and runtime token resolution already accept SecretRef values, but the TypeScript type was still `string`. Update to `SecretInput` so the type layer matches. Closes openclaw#32445 Co-Authored-By: Claude Opus 4.6 <[email protected]>
c21aaba to
e6faa09
Compare
Contributor
|
Merged via squash. Thanks @scoootscooob! |
MillionthOdin16
added a commit
to MillionthOdin16/openclaw
that referenced
this pull request
Mar 3, 2026
Summary
DiscordAccountConfig.tokenfromstringtoSecretInput(string | SecretRef) in the TypeScript type layerSecretInputSchema) and runtime resolution (normalizeResolvedSecretInputString) already supportSecretRefvalues (landed in feat(secrets): expand SecretRef coverage across user-supplied credentials #29580), but the TS type was stillstringSecretReftokensTest plan
tsc --noEmitpasses (no new type errors)Closes #32445
🤖 Generated with Claude Code