NN-3681: document typed WhatsApp recipients - #1
Merged
Conversation
leandronvoip
marked this pull request as ready for review
July 28, 2026 20:52
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
2 participants
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.
O que mudou
Adiciona o contrato compatível
destinationourecipient={type,value}, cobrindophone,bsuideparent_bsuid, com exclusividade e rejeição de@username. BSUID nunca é tratado ou persistido como telefone.Por quê
Alinha este repositório ao outbound das APIs V2/V3 do NN-3681 e evita destinos ambíguos.
Impacto
Somente exemplos/documentação; não altera o runtime do SDK.
Validação
javac, revisão do diff e gatepre-prpassaram. Nenhum envio WhatsApp ou acesso a PII foi realizado.