-
Notifications
You must be signed in to change notification settings - Fork 65
feat: add name support to email 'to' field, matching cc/bcc format #114
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
19684f5
feat: add Recipient value object for named email recipients
ChiragAgg5k 842c112
fix: update all tests to use Recipient value object
ChiragAgg5k d1213e0
fix: address PR review comments
ChiragAgg5k f1356bf
feat: make Recipient value object non-breaking
ChiragAgg5k b293444
refactor: remove Recipient class, unify to/cc/bcc as arrays
ChiragAgg5k 33a07cc
fix: address code review findings
ChiragAgg5k 92aaa27
fix: assert correct deliveredTo count in mixed-format test
ChiragAgg5k cf050ec
chore: bump PHP requirement to 8.1+, use first-class callables
ChiragAgg5k File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
h:Reply-Toentry is a numeric-indexed value, not a keyed headerThe array entry on this line is missing the
=>assignment operator, so the entire string'h:Reply-To: Name <email>'is stored as a numeric-indexed element (e.g.$body[0]). When form-encoded and sent to Mailgun this becomes0=h%3AReply-To%3A+...rather than theh:Reply-Tocustom-header field Mailgun expects. The Reply-To header is therefore silently never forwarded.This is a pre-existing bug, but this PR already touches the line (adding the RFC 5322 space), making it the natural place to fix it: