Closed sras closed 7 years ago
We need to ensure the following:
@saurabhnanda
You want to put the code that send activation email in the createTenant api function? Would't that be a bit out of scope of it's responsibility?
Isn't this something that the library should do internally and expose via an API method?
The library exposes api methods to set headers. Isn't setting specific headers trivial enough to leave those from the api? Also, I am not sure if a general api method is even possible in this case. Because if you have a mail prepared, how will you specify a particular content block in it?
You want to put the code that send activation email in the createTenant api function? Would't that be a bit out of scope of it's responsibility?
If you feel that, do the following:
The library exposes api methods to set headers. Isn't setting specific headers trivial enough to leave those from the api? Also, I am not sure if a general api method is even possible in this case. Because if you have a mail prepared, how will you specify a particular content block in it?
Why is it not possible for the library API to insert an attachment with a given CID? Or insert an attachment and return an auto-generated CID, guaranteed to be unique in context of the email?
PR for mime-email library accepted at https://github.com/snoyberg/mime-mail/pull/48 and version updated at https://hackage.haskell.org/package/mime-mail-0.4.12/docs/Network-Mail-Mime.html
Sprint 3: Find and implement solution for Transactional emails.
Time 2 days.