Skip to content
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

Changes for sending mail before the job is scheduled, as part of sanity check for users #33

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

harshchiki
Copy link

Issue link: #31

@abhilashkulkarniofficial , could you please review. I have tested and sharing below the screenshot.

image

abhilashkulkarniofficial and others added 4 commits May 2, 2021 14:56
* Changed email body

Added html email template to the email body to display the slots information in a cleaner template.

* Removed bug in creating template

* Updated Readme to add new email template
Revert was done as createTemplate method iterates on a string, and throws errors.

This reverts commit f04624d.
@@ -14,7 +14,7 @@ exports.sendEmail = function (email, subjectLine, slotDetails, callback) {
from: String('Vaccine Checker ' + process.env.EMAIL),
to: email,
subject: subjectLine,
text: 'Vaccine available. Details: \n\n' + slotDetails
text: slotDetails
};
nodemailerTransporter.sendMail(options, (error, info) => {
Copy link
Author

Choose a reason for hiding this comment

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

I hope this takes care of a misconfiguration (or anything) - and throws up if the mail could not be sent.

@harshchiki
Copy link
Author

@roronoazabuza

image
status-stopped (shows likr this after doing changes in both files)
please guide..

Assuming you are facing this issue with the changes of the PR applied. Can you confirm, if you are seeing the same on the current master branch (essentially ruling out the changes of this PR)?

@roronoazabuza
Copy link

@roronoazabuza

image
status-stopped (shows likr this after doing changes in both files)
please guide..

Assuming you are facing this issue with the changes of the PR applied. Can you confirm, if you are seeing the same on the current master branch (essentially ruling out the changes of this PR)?

image
it shows like this for original code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants