/send/carousel splits message into two bubbles (Text + Cards) instead of sending one unified message
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start at the Go /send/carousel handler and trace how it currently calls sendTextMessage and sendCarousel. Inspect the interactive message payload construction for the top-level body and footer. Done means the endpoint produces one WhatsApp interactive carousel bubble containing the body, footer, and cards, rather than two separate messages.
Written by the indexing model from the issue text.
Description
Welcome!
- Yes, I have searched for similar issues on GitHub and found none.
What did you do?
Currently, when sending a carousel message using the /send/carousel endpoint with a top-level "body" and "footer", the Evolution Go server splits the payload and sends it as two separate messages on WhatsApp:
First bubble: A standard text message containing main text and footer.
Second bubble: The actual interactive cards carousel.
This creates a disconnected user experience. WhatsApp’s native interactive protocol supports binding the main body text, footer, and the sliding carousel cards together inside one single interactive message bubble.
What did you expect?
The recipient should receive only one single interactive message bubble where the body text ("Special offers from Royalty Tours 🌸") and footer text ("Click below to see details") reside directly above the sliding cards within the same bubble.
What did you observe instead of what you expected?
Instead of splitting the payload into a separate sendTextMessage call and a sendCarousel call, the Go handler should compile the top-level body and footer directly into the interactive message payload as the main interactive text header/body, so that the WhatsApp client renders everything together in one single bubble.
Screenshots/Videos
No response
Which version are you using?
0.7.1
What is your environment?
Docker
If applicable, paste the log output
No response
Additional Notes
No response
- Dominant language
- Go
- Stars
- 918
- Forks
- 488
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evolution-foundation/evolution-go
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
evolution-foundation/evolution-go#193 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
evolution-foundation/evolution-go#104 ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
evolution-foundation/evolution-go#101 ·
Maintainers usually reply within 5 days
-
POST /group/participant always returns 400 "participants is required and cannot be empty" (wrong validation middleware on route)Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
evolution-foundation/evolution-go#97 · 2 comments ·
Maintainers usually reply within 5 days
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 42/100
evolution-foundation/evolution-go#217 ·
Maintainers usually reply within 5 days
All issues in evolution-foundation/evolution-go
Similar issues
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
FairwindsOps/nova#484 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
automated-analysis code-quality cookie
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
github/gh-aw#67517 · 3 comments ·
Maintainers usually reply within 1 day
-
[otelcol] print-config help text still requires the removed otelcol.printInitialConfig feature gatePossibly taken @girishkvs claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/opentelemetry-collector#16143 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue load-balancing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ktrubilo9/edge-proxy#53 ·