1dfaf8c5f8
no issue The email table should be a reference for all data that was used when sending an email. From and Reply-to addresses can change over time and we don't have any other reference for their value at the time of sending an email so we should store them alongside the email content. - schema updated with `from` and `reply_to` columns - both are set to `nullable` because we don't have historic data (can be populated and changed in later migrations if needed) - neither `from` or `reply_to` have `isEmail` validations because they can have name+email in an email-specific format - will help keep concerns separated in the future. `mega` service can deal with all of the email contents/properties, and the `bulk-email` service's concerns are then only email sending and any provider-specific needs |
||
|---|---|---|
| .. | ||
| api-acceptance | ||
| frontend-acceptance | ||
| regression | ||
| unit | ||
| utils | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .jshintrc | ||