Kevin Ansfield 1dfaf8c5f8 Added migration to store from/reply-to values in email table (#12204) ... 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		2020-09-24 08:20:10 +01:00
..
db	Updated var declarations to const/let and no lists	2020-04-29 16:51:13 +01:00
exporter	Removed use of deprecated setting flags from the codebase	2020-06-23 11:58:19 +12:00
importer	Cleaned up members & stripe settings (#11957)	2020-06-29 16:22:42 +02:00
meta	Moved core/server/lib/url-utils to core/shared/url-utils (#11856)	2020-05-28 11:57:02 +01:00
migrations	Added migration utils for permissions	2020-06-25 19:15:25 +02:00
schema	Added migration to store from/reply-to values in email table (#12204)	2020-09-24 08:20:10 +01:00
validation	Improved settings validation (#12048)	2020-07-15 17:11:27 +02:00
xml/sitemap	Removed final non-destructured imports of core/server/lib/common (#11858)	2020-05-28 17:54:18 +01:00