Telegram: fix dock native command registration#929
Telegram: fix dock native command registration#929grp06 wants to merge 4 commits intoopenclaw:mainfrom
Conversation
4037eb5 to
0de3a1a
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4037eb5ef3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| defineChatCommand({ | ||
| key: `dock:${dock.id}`, | ||
| nativeName: `dock-${dock.id}`, | ||
| nativeName: `dock_${dock.id}`, | ||
| description: `Switch to ${dock.id} for replies.`, | ||
| textAlias: `/dock-${dock.id}`, |
There was a problem hiding this comment.
Keep dock command text alias aligned with native name
nativeName now uses dock_${dock.id} while the only text alias remains /dock-${dock.id}. The command parser (normalizeCommandBody/hasControlCommand) only recognizes textAliases, but /commands output uses nativeName as the primary label (see buildCommandsMessage in src/auto-reply/status.ts). In text-only contexts (e.g., commands.native disabled or surfaces without native commands), users will be shown /dock_… yet that string is not a recognized alias, so the command won’t be handled. Consider adding a /dock_${dock.id} text alias or switching the primary label to the text alias when native commands are off.
Useful? React with 👍 / 👎.
# Conflicts: # CHANGELOG.md
0de3a1a to
b0e5e00
Compare
Thanks @grp06. Co-authored-by: George Pickett <gpickett00@gmail.com>
Thanks @grp06. Co-authored-by: George Pickett <gpickett00@gmail.com>
Summary
Testing
Notes