-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(brevo) : Hide contacts properly for all sources #303
base: main
Are you sure you want to change the base?
Conversation
SELECT DISTINCT | ||
UNNEST(contact_uids) AS id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SELECT DISTINCT | |
UNNEST(contact_uids) AS id, | |
SELECT | |
DISTINCT UNNEST(contact_uids) AS id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
c'est pas moi c'est sqlfluff.
When a contact has stated an opposition and/or has been blacklisted, handle it correctly, whatever the source. This time, it is also properly tested.
cc040bf
to
2b66370
Compare
Je m'attends à une relecture plus musclée :) |
@vmttn cette PR est un peu tricky je serais content d'avoir ton avis à ce sujet. @Caldagues je vais ajouter à cette PR l'implémentation pour cacher les contacts d'une structure également si on a eu opposition sur un email venant d'un service. |
Tickets traités:
Bloquer les contacts venant de mes-aides & mediation-numerique apres une opposition Brevo
==> celui-ci est généralisé à toute source
Ne pas supprimer certaines coordonnées lors d'un hardbounce Brevo