Skip to content
This repository has been archived by the owner on Jul 19, 2022. It is now read-only.

Drop dependency on the jellyfish-mail package #947

Merged
3 commits merged into from
Feb 8, 2022

Conversation

LucianBuzzo
Copy link
Contributor

The abstraction inside jellyfish-mail can be held entirely inside the
action-send-email action, allowing us to archive the whole
jellyfish-mail repo.

Change-type: patch
Signed-off-by: Lucian Buzzo lucian.buzzo@gmail.com

The abstraction inside `jellyfish-mail` can be held entirely inside the
`action-send-email` action, allowing us to archive the whole
`jellyfish-mail` repo.

Change-type: patch
Signed-off-by: Lucian Buzzo <lucian.buzzo@gmail.com>
It doesn't make sense to include the `buildSendEmailOptions` utility
inside the `action-send-email` file, since its not actually used there.

Change-type: patch
Signed-off-by: Lucian Buzzo <lucian.buzzo@gmail.com>
Change-type: patch
Signed-off-by: Josh Bowling <josh@balena.io>
@@ -81,13 +81,13 @@ const handler: ActionDefinition['handler'] = async (
defaultEnvironment.mail.options
) {
const client = new Mailgun(defaultEnvironment.mail.options);
const response = await client.sendEmail({
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an axios response object typed as any and therefore doesn't match what we expect to be returned from action handlers. null is the best option here as we aren't creating/updating contracts etc, we're just attempting to send an email through an external service.

@ghost ghost merged commit dd01d32 into master Feb 8, 2022
@ghost ghost deleted the lucianbuzzo/deprecate-jellyfish-mail branch February 8, 2022 01:54
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants