docs: EncHandler wasm portability (whatsapp-rust#793) - #279
Conversation
- Append EncHandler wasm fix to changelog/2026-06-09.mdx - Add wasm Note to with_enc_handler section in api/bot.mdx
|
Warning Review limit reached
More reviews will be available in 20 minutes and 7 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Summary
Documents the fix from oxidezap/whatsapp-rust#793, which relaxed
EncHandler'sSend + Syncsupertrait toMaybeSendSyncand added a wasm32-gatedasync_trait(?Send).Files changed:
changelog/2026-06-09.mdx— Added anEncHandlerwasm portability entry to the "Fixes & hardening" section.api/bot.mdx— Added a<Note>to thewith_enc_handlersection explaining that!SendJS handles are allowed onwasm32, while native targets keepSend + SyncviaMaybeSendSync.What changed in the library
EncHandler(the custom enc extension point registered viaBotBuilder::with_enc_handler) previously requiredSend + Syncunconditionally, making it impossible to implement with!SendJS handles on the wasm32 port. The fix mirrors howEventHandlerandSendContextResolveralready handle this: useMaybeSendSyncas the supertrait and gateasync_traitwith?Sendon wasm32. Native behaviour is unchanged.Generated by Claude Code