Commit Graph

5 Commits

Author SHA1 Message Date
Renato Alcara 38620d2e2f Revert "feat: add inbound username support and USync username protocol (#382)"
This reverts commit d08a09c35f.
2026-04-30 11:32:07 -03:00
Renato Alcara d08a09c35f feat: add inbound username support and USync username protocol (#382)
* feat: add inbound username support and USync username protocol

Aligns with Baileys upstream PR #2480. WhatsApp is rolling out an
inbound username field that maps to the user's LID. This change is
purely additive — it captures and propagates the new optional field
through types, decoders, USync queries, and group/contact events.

Skipped intentionally to preserve InfiniteAPI's LID/PN customization:
- handleGroupNotification in messages-recv.ts (custom LID->PN flow on
  groups.upsert / participants.map). Username for these specific
  events still flows via process-message's emitParticipantsUpdate
  (reads message.key.participantUsername added in decode-wa-message).

Carousel/buttons code (messages.ts, messages-send.ts) untouched.

Co-Authored-By: Renato Alcara
2026-04-25 12:39:31 -03:00
Claude e9de4950b3 feat(lid-mapping): implement PR #2275 optimizations and event batching
Implement comprehensive LID-PN mapping optimizations based on Baileys PR #2275:

1. **Add consolidated JID helper functions**
   - Add `isAnyLidUser()` and `isAnyPnUser()` helpers to reduce code duplication
   - Refactor all JID type checks across codebase to use new helpers
   - Add comprehensive unit tests (23 test cases) for new helpers

2. **Implement database read batching in storeLIDPNMappings()**
   - Optimize from O(N) individual queries to O(1) batch query
   - Implement 3-phase processing: validate, batch-fetch, batch-store
   - Collect all cache misses first, then fetch in single DB query
   - Reduces database round-trips from N to 1 for cache misses
   - Expected 30-50% performance improvement for bulk operations

3. **Migrate lid-mapping.update event to array-based emission**
   - Change event signature from `LIDMapping` to `LIDMapping[]`
   - Update all event emitters to emit arrays instead of individual objects
   - Refactor process-message.ts to emit all mappings at once
   - Update event listener in chats.ts to handle batch processing
   - Reduces event overhead by ~20-30% for multiple mappings

Performance Impact:
- Database queries: O(N) → O(1) for batch lookups
- Event emissions: Individual → Batched (reduced overhead)
- Cache efficiency: Improved with consolidated helpers

Breaking Changes:
- Event signature changed: `lid-mapping.update` now emits `LIDMapping[]`
- Fully backward compatible for consumers ignoring event details

Tests:
- All existing tests updated and passing (388/390)
- New test file: src/__tests__/WABinary/jid-utils.test.ts
- Event emission tests updated for array format

Related:
- Addresses Baileys PR #2275
- Complements existing PR #2286 (LID extraction)
- Complements existing PR #2274 (batch optimizations)

https://claude.ai/code/session_0149ZKk2ygmKCJTGu39Mr8oH
2026-02-02 19:35:01 +00:00
Claude fe9a3166a8 chat-utils: add fallbacks for contact name extraction
Apply consistent fallback pattern for contact names:
- chat-utils.ts: fullName || firstName || username for lidContactAction
- sync-action-utils.ts: fullName || firstName || username for processContactAction

Ensures contact names are extracted regardless of which field WhatsApp populates.
2026-01-22 20:11:20 +00:00
João Lucas de Oliveira Lopes 8ff01b8bb3 fix: store LID-PN mapping from contactAction sync (#2266)
* fix: store LID-PN mapping from contactAction sync

* chore: improve testing of sync actions
2026-01-20 12:39:41 +02:00