-
-
Notifications
You must be signed in to change notification settings - Fork 19
feat: add AWS SES payload adapter #65
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
Thanks for opening this pull request!
|
Codecov ReportBase: 100.00% // Head: 100.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## alpha #65 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 8 8
Lines 515 546 +31
Branches 41 47 +6
=========================================
+ Hits 515 546 +31
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I'm embarassed to say that I didn't see the tests before :) I'll take a look at them and try to fix the coverage issue, as well as these other issues. |
I will reformat the title to use the proper commit message syntax. |
@mtrezza let me know if you need me to tackle anything else. |
I've pushed the suggested changes. Not sure I should be the one to resolve those, sorry. I should have checked with you first. |
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.
Looks good! Waiting for CI to pass, then let's merge!
…-api-mail-adapter into ses-provider
I refactored the payload converter to remove some code duplication. The test pass, so it should be fine, but could you still just check whether this works? |
Yes, all still works! 💪 |
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.
Looks good! Thanks for adding the SES converter!
# [2.1.0-alpha.9](2.1.0-alpha.8...2.1.0-alpha.9) (2022-09-15) ### Features * add AWS SES payload adapter ([#65](#65)) ([4ecc4c9](4ecc4c9))
🎉 This pull request has been released in version 2.1.0-alpha.9 |
Thanks for your patience! I've learned a lot through the process. My next contribution will be of a higher quality:) |
@mtrezza I see npm has been updated with the new release number, yet the ses provider is not present. Am I missing something? Please forgive me if I've got my wires crossed! |
What do you mean by "not present"? |
Hi, I've deleted the lock file, node_modules and ensured that v 2.1.0 is
installed, but I still see the previous version - i.e. without the ses
converter.
When I look on npm, the readme
<https://www.npmjs.com/package/parse-server-api-mail-adapter> is also the
previous version. i.e. without the ses converter.
…On Thu, Sep 15, 2022 at 4:08 PM Manuel ***@***.***> wrote:
yet the ses provider is not present
What do you mean by "not present"?
If you look at the source code in node_modules, it should be there. Maybe
you are looking at a different version? Try to delete the node_modules
and package-lock.json file in your app and run npm i. Also make sure you
have added the correct adapter version in package.json.
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEIB74HWEZGW6GLYVJFF6DV6MUUJANCNFSM6AAAAAAQLGZ3LM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
--
----------------------------------------------
*Wouter* Couvaras
+27 (0) 79 878 6294
*www.hootoriginals.com* <http://www.hootoriginals.com>
----------------------------------------------
Disclaimer: If you are not the addressee indicated in this message (or
responsible for delivery of the message to such person), you may not copy
or deliver this message to anyone - you should destroy this message and
kindly notify the sender by reply email. Content in this message that do
not relate to the official business of my employer, being Hoot Originals,
shall be understood as neither given nor endorsed or authorised by it.
Although all reasonable care is taken to transmit this message free of any
damaging code, Hoot Originals and the sender do not make any warranties in
this regard whatsoever and cannot be held liable for any loss or damages
incurred by the recipient.
*© Hoot Originals 2019. *All rights reserved.
|
You need to look at the right version: https://www.npmjs.com/package/parse-server-api-mail-adapter/v/2.1.0-alpha.9#providers The item is missing in the index (I'll correct that), but if you scroll to the text it's there. |
Gotcha, thanks!
…On Fri, Sep 16, 2022 at 10:27 AM Manuel ***@***.***> wrote:
You need to look at the right version:
https://www.npmjs.com/package/parse-server-api-mail-adapter/v/2.1.0-alpha.9#providers
The item is missing in the index, but if you scroll to the text it's there.
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEIB77LOBTOPX7PWXGNDH3V6QVO3ANCNFSM6AAAAAAQLGZ3LM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
--
----------------------------------------------
*Wouter* Couvaras
+27 (0) 79 878 6294
*www.hootoriginals.com* <http://www.hootoriginals.com>
----------------------------------------------
Disclaimer: If you are not the addressee indicated in this message (or
responsible for delivery of the message to such person), you may not copy
or deliver this message to anyone - you should destroy this message and
kindly notify the sender by reply email. Content in this message that do
not relate to the official business of my employer, being Hoot Originals,
shall be understood as neither given nor endorsed or authorised by it.
Although all reasonable care is taken to transmit this message free of any
damaging code, Hoot Originals and the sender do not make any warranties in
this regard whatsoever and cannot be held liable for any loss or damages
incurred by the recipient.
*© Hoot Originals 2019. *All rights reserved.
|
# [2.1.0-beta.2](2.1.0-beta.1...2.1.0-beta.2) (2023-01-24) ### Bug Fixes * bump nanoid from 3.1.29 to 3.2.0 ([#56](#56)) ([76a374b](76a374b)) * bump trim-off-newlines from 1.0.1 to 1.0.3 ([#57](#57)) ([794cfb6](794cfb6)) * security upgrade minimist from 1.2.5 to 1.2.6 ([#59](#59)) ([1a5253f](1a5253f)) * security upgrade node-fetch from 2.6.1 to 2.6.7 ([#60](#60)) ([576d336](576d336)) * security upgrade semver-regex from 3.1.3 to 3.1.4 ([#62](#62)) ([4db06d2](4db06d2)) ### Features * add AWS SES payload adapter ([#65](#65)) ([4ecc4c9](4ecc4c9))
🎉 This pull request has been released in version 2.1.0-beta.2 |
# [2.2.0](2.1.0...2.2.0) (2023-01-24) ### Bug Fixes * bump nanoid from 3.1.29 to 3.2.0 ([#56](#56)) ([76a374b](76a374b)) * bump trim-off-newlines from 1.0.1 to 1.0.3 ([#57](#57)) ([794cfb6](794cfb6)) * security upgrade minimist from 1.2.5 to 1.2.6 ([#59](#59)) ([1a5253f](1a5253f)) * security upgrade node-fetch from 2.6.1 to 2.6.7 ([#60](#60)) ([576d336](576d336)) * security upgrade semver-regex from 3.1.3 to 3.1.4 ([#62](#62)) ([4db06d2](4db06d2)) ### Features * add AWS SES payload adapter ([#65](#65)) ([4ecc4c9](4ecc4c9))
# [2.2.0](2.1.0...2.2.0) (2023-01-24) ### Bug Fixes * bump nanoid from 3.1.29 to 3.2.0 ([#56](#56)) ([76a374b](76a374b)) * bump trim-off-newlines from 1.0.1 to 1.0.3 ([#57](#57)) ([794cfb6](794cfb6)) * security upgrade minimist from 1.2.5 to 1.2.6 ([#59](#59)) ([1a5253f](1a5253f)) * security upgrade node-fetch from 2.6.1 to 2.6.7 ([#60](#60)) ([576d336](576d336)) * security upgrade semver-regex from 3.1.3 to 3.1.4 ([#62](#62)) ([4db06d2](4db06d2)) ### Features * add AWS SES payload adapter ([#65](#65)) ([4ecc4c9](4ecc4c9))
🎉 This pull request has been released in version 2.2.0 |
New Pull Request Checklist
Issue Description
Add support for an AWS SES Adapter
Related issue: #64
Approach
Very simply, I've just added a transformer to match the required SES payload for the v3 SDK.
I've also updated two parameter names in the documentation as they did not match the original Parse payload I was receiving. I've also added an example of how to use it in the docs.
This is my first ever open source PR, so happy for any guidance :)
TODOs before merging