Feature/email system integration 44

[14mT]

Issues

Closes #

Description

Email System Integration #44

Created an email system with Resend with a field of: the recipient, subject of the email, and its content. The API key have been stored securely (in .env at the moment) and not hardcoded anywhere. The system can be reused for different features (as demonstrated with the welcome function).

Some testing proof:

(earliest testing success - email was able to be sent)

(successful email sent to an actual email at the creation of a new user account - _without_ using the welcome email function) (successful email sent to an actual email at the creation of a new user account - _with_ using the welcome email function)

Checklist:

• An email adapter / provider has been configured through Payload (v)
• Email recipient, subject, and content can be configured dynamically (v)
• Failed email attempts are handled safely (?)
• Sensitive configuration values (i.e. API keys) are stored securely and not hardcoded (v)
• Email functionality is reusable for future features (v)
• Test emails can be sent through the system (v)
• Tested (independently of frontend integration) and shows expected results (v)

NOTES:

• I changed the user.ts to become user.tsx after an error was raised as I was about to test the welcome email function, caused by using react email in said function.
• The API key that I used was a personal one that I created myself (in the .env file).

Checklist

• [v] Make sure you are requesting to pull a feature/fix branch (right side). Don't request the main branch!
• [v] Make sure you are making a pull request against the main branch (left side). Also you should start your branch off main branch.
• [v] I have added tests that prove my fix is effective or that my feature works.
• [v] I have added the necessary documentation (if appropriate).

How To Review

payload.config.ts
send_email.ts
welcome.tsx
user.tsx

Notes