Ghost/ghost/milestones/lib/milestones.js

module.exports.InMemoryMilestoneRepository = require('./InMemoryMilestoneRepository');
module.exports.MilestonesService = require('./MilestonesService');
module.exports.MilestoneCreatedEvent = require('./MilestoneCreatedEvent');
module.exports.Milestone = require('./Milestone');
Added initial basic milestone emails in-memory repository (#16216) refs https://www.notion.so/ghost/Marketing-Milestone-email-campaigns-1d2c9dee3cfa4029863edb16092ad5c4 This adds a milestone entity and in-memory repository in a new `milestone-emails` package. This also adds a first initial definition of milestones and their types which is held in the default config to avoid DB changes when, e. g. values change. This should get everything in place to begin with the service implementation. 2023-02-07 13:47:35 +03:00			`module.exports.InMemoryMilestoneRepository = require('./InMemoryMilestoneRepository');`
Renamed milestone-emails to milestones no issue - The way we're going to implement milestones diverged from the original idea of handling email sending within the milestone-emails package, as we'll be sending events instead and will utilise the StaffService to listen to them and send the emails - This renames the package as well as the service in core itself and all relevant tests 2023-02-15 10:23:31 +03:00			`module.exports.MilestonesService = require('./MilestonesService');`
Exposed `MilestoneCreatedEvent` as module 2023-02-15 14:57:55 +03:00			`module.exports.MilestoneCreatedEvent = require('./MilestoneCreatedEvent');`
Added `BookshelfMilestoneRepository` implementation (#16305) refs https://www.notion.so/ghost/Marketing-Milestone-email-campaigns-1d2c9dee3cfa4029863edb16092ad5c4?pvs=4 This stores the received milestones in the database. 2023-02-22 16:53:29 +03:00			`module.exports.Milestone = require('./Milestone');`