crashlabs/huskies
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 26 Wiki Activity

storkit: create 404_bug_whatsapp_and_slack_missing_assign_command_handler

Browse Source
This commit is contained in:
dave
2026-03-26 20:05:40 +00:00
parent a52d1e098f
commit de54265c35
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.storkit/work/1_backlog/404_bug_whatsapp_and_slack_missing_assign_command_handler.md
+7 -1
View File
@@ -10,7 +10,13 @@ The assign command has a fallback handler in chat/commands/mod.rs that returns N
## Implementation Note
The fix must be in the shared command dispatch layer (chat/commands/mod.rs), NOT by adding transport-specific handlers. Study how commands like "rebuild" and "status" already work through the shared dispatch — the assign handler should return a concrete result from try_handle_command so all transports get it for free. We do not want separate mechanisms per transport per command.
Follow the **rebuild pattern** established in story 402.
- `extract_assign_command` and `handle_assign` already exist in `server/src/chat/transport/matrix/assign.rs`
- Add an async intercept in `server/src/chat/transport/whatsapp.rs` (see rebuild intercept ~line 1107) and `server/src/chat/transport/slack.rs` (see rebuild intercept ~line 845)
- Call `crate::chat::transport::matrix::assign::extract_assign_command` to detect the command, then `crate::chat::transport::matrix::assign::handle_assign` to execute it
- The fallback handler in `chat/commands/mod.rs` (`handle_assign_fallback` — note: the registry entry for `assign` currently calls `assign::handle_assign` synchronously; verify this doesn't conflict) stays as-is for `help` listing
- The fallback in `chat/commands/assign.rs` may need to return `None` instead of a real response once the async path handles it
## How to Reproduce