feat: WhatsApp Groups support — frontend#63
Merged
Conversation
- ChatListItem: group icon badge on group conversations - ChatHeader: group icon + "Grupo" label for group conversations - New conversation: tabs (Contacto/Grupo), group creation form - Only available for Cloud API numbers (not Coexistence) - Creates group via whatsapp-management endpoint - Integration settings: Cloud API / Coexistence labels - Warning note for Coexistence: groups not available - English translations for all new strings Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Always show Contacto/Grupo tabs when WhatsApp numbers exist. If only Coexistence numbers, show message explaining groups require Cloud API. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Match the existing filter pill design (border, rounded-full) instead of custom solid buttons. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Single number: shows info text. Multiple numbers: shows dropdown to select which number creates the group. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
zuccoligerman
commented
May 29, 2026
zuccoligerman
left a comment
zuccoligerman
left a comment
Contributor
Author
There was a problem hiding this comment.
Revisé el cambio (5 archivos, +208/-26). UI limpia para WhatsApp Groups:
- ChatListItem/ChatHeader: Ícono de grupo (
Users) + label "Grupo". Correcto, sigue patrones existentes. - New conversation: Tabs Contacto/Grupo con form de creación. Cloud API vs Coexistence detection correcta.
useMutationpara la llamada. Bien hecho. - Integration settings: Labels Cloud API/Coexistence + warning para usuarios de Coexistence. Correcto.
- i18n: Traducciones en en.json completas.
Pregunta:
- En
new.tsx, el form llamasupabase.functions.invoke("whatsapp-management", { method: "POST", headers: { "x-action": "groups" }, body: {...} }). Pero en wakit-api#29 la ruta Hono esapp.post("/whatsapp-management/groups", ...). ¿El headerx-action: "groups"se traduce a la sub-ruta/groupsen algún middleware? Si no, el request podría ir al root del Edge Function sin matchear la ruta de grupos.
No puedo aprobar (token=autor). — Atlas
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Companion PR
Backend: MirloLLC/wakit-api#29
Test plan
🤖 Generated with Claude Code