-
Notifications
You must be signed in to change notification settings - Fork 0
docs: document 🦀send command (whatsapp-rust#875) #338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| --- | ||
| title: "June 15, 2026 — Example bot: 🦀send command" | ||
| description: "Adds a 🦀send <jid> <text> command that you can use in the demo bot to relay text to any group or DM JID and report send latency back to the originating chat." | ||
| --- | ||
|
|
||
| PR [`#875`](https://github.com/oxidezap/whatsapp-rust/pull/875) adds a `🦀send` command that you can use in the demo bot in `src/main.rs`. | ||
|
|
||
| ## What changed | ||
|
|
||
| The example bot now handles `🦀send <jid> <text>` in addition to `🦀ping`. When you send this command from any chat, the bot relays the text to an arbitrary JID — a group (`...@g.us`) or DM (`...@s.whatsapp.net`) — then replies in the originating chat with the send latency via `ctx.reply_quoting`. | ||
|
|
||
| ``` | ||
| 🦀send 1234567890@s.whatsapp.net Hello there! | ||
| ``` | ||
|
|
||
| The reply in the originating chat looks like: | ||
|
|
||
| ``` | ||
| âś… Sent to 1234567890@s.whatsapp.net | ||
| `3.42ms` | ||
| ``` | ||
|
|
||
| ## Implementation notes | ||
|
|
||
| The handler uses `split_once(char::is_whitespace)` to split the JID and message text in a single pass with no intermediate `Vec`. The JID is validated through `FromStr` — invalid JIDs are logged and the handler returns early. All failures (missing args, bad JID, send error) are logged rather than panicking, matching the rest of the example bot. | ||
|
|
||
| The message handler was also refactored to hoist the `text_content()` guard into a single `let … else { return }` at the top, avoiding repeated calls and making it straightforward to add new text-triggered commands. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the relayed text itself starts with
🦀send, this branch will also run for the bot's own sent-message fanout unless the handler checksctx.info.source.is_from_mefirst. A user can send one nested relay command and have the bot reinterpret its own relayed message as another command, causing unintended extra sends (or command chains) from the bot account; add a self-message guard before dispatchinghandle_send_command.Useful? React with 👍 / 👎.