Fixes #70 and allows usage of duplicate recipients#71
Merged
Conversation
aayush-sib
previously approved these changes
Nov 9, 2022
xhit
requested changes
Nov 10, 2022
xhit
left a comment
xhit
left a comment
Owner
There was a problem hiding this comment.
Hi, thanks for the PR and sorry for delay. I left some comments before merge and tag release.
mukul-brevo
requested review from
aayush-sib and
xhit
and removed request for
aayush-sib and
xhit
|
Thanks a lot @xhit for the quick action 🙂 |
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
3 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.
This change adds the functionality to allow usage of duplicate recipients (if present).
This can be achieved by setting
DuplicateRecipientAllowedflag astrue(shown below for reference)