Labels for WhatsApp Business accounts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- desktop-dev
Research direction
Start with AGENTS.md for the privacy rules and translation requirements, then read the labels() API and the LabelEditUpdate and LabelAssociationUpdate events at the pinned whatsapp-rust revision ae3cefd. The issue lists three separate pieces of work (showing and filtering labels, managing labels, applying label events), so agree on a split with a maintainer before coding. Done means labels appear on chats, the chat list can be filtered by them, label changes from other devices show up, and new strings have pt_BR translations.
Written by the indexing model from the issue text.
Description
A WhatsApp feature that whatsapp-rust already supports but ZapTide does not use yet.
What whatsapp-rust provides
Checked against the pinned revision ae3cefd:
labels() offers create_label, delete_label, add_chat_label, remove_chat_label, add_message_label and remove_message_label, and the events LabelEditUpdate and LabelAssociationUpdate.
What ZapTide does today
Nothing. Labels created on the phone are not shown.
Proposed scope
- Show labels on chats and filter the chat list by label.
- Create, edit and delete labels, and add them to chats and messages.
- Apply the two label events from other devices.
Notes
The privacy rules in AGENTS.md apply: no message content in logs or tests. New strings need a pt_BR translation.
- Dominant language
- Rust
- Stars
- 29
- Forks
- 1
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 36
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 luminusOS/zaptide
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
luminusOS/zaptide#88 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
luminusOS/zaptide#85 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
luminusOS/zaptide#84 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
luminusOS/zaptide#83 · 2 comments ·
Maintainers usually reply within 1 day
-
Appimage - Some icons are not showingPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
luminusOS/zaptide#77 · 3 comments ·
Maintainers usually reply within 1 day
All issues in luminusOS/zaptide
Similar issues
-
desktop documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
vfarcic/dot-agent-deck#2008 ·
Maintainers usually reply within 1 day
-
L: javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dependabot/dependabot-core#16744 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nautechsystems/nautilus_trader#5486 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Bump rustls-webpki, webpki-roots and webpki-root-certs for the emSign distrust (CVE-2026-111943)Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day