-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Notifier] Add Esendex message ID to SentMessage object #42748
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
Conversation
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
src/Symfony/Component/Notifier/Bridge/Esendex/Tests/EsendexTransportTest.php
Outdated
Show resolved
Hide resolved
src/Symfony/Component/Notifier/Bridge/Esendex/EsendexTransport.php
Outdated
Show resolved
Hide resolved
The Esendex API request returns a unique message ID for each SMS sent. This commit simply extracts the message ID and adds it to the returned SentMessage object.
@@ -1,6 +1,8 @@ | |||
CHANGELOG | |||
========= | |||
|
|||
* Add returned message ID to `SentMessage` |
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.
* Add returned message ID to `SentMessage` | |
5.4 | |
--- | |
* Add returned message ID to `SentMessage` |
Thank you @benr77. |
The Esendex API request returns a unique message ID for each SMS sent.
This commit simply extracts the message ID and adds it to the returned SentMessage object.