mirror of
https://github.com/TryGhost/Ghost.git
synced 2025-02-10 23:36:14 -05:00
no issue We want to store a list of recipients for each bulk email so that we have a consistent set of data that background processing/sending jobs can work from without worrying about moving large data sets around or member data changing mid-send. - `email_batches` table acts as a join table with status for email<->email_recipient - stores a provider-specific ID that we get back when submitting a batch for sending to the bulk email provider - `status` allows for batch-specific status updates and picking up where we left off when submitting batches if needed - explicitly tying a list of email recipients to a batch allows for partial retries - `email_recipients` table acts as a join table for email<->member - `member_id` does not have a foreign key constraint because members can be deleted but does have an index so that we can efficiently query which emails a member has received - stores static copies of the member info present at the time of sending an email for consistency in background jobs and auditing/historical data |
||
---|---|---|
.. | ||
admin | ||
content | ||
README.md |
Acceptance Tests
This folder should only contain a set of basic API use cases.
We are currently refactoring the test env. The "old" folder currently contains all API tests for the stable API version (v2). The goal is:
- either keep a test if it's a basic use case e.g. upload an image, schedule a post, download a theme
- otherwise move the test to regression api v2 tests
We probably need a differentiation for the acceptance tests for session and api_key authentication.
Before we move tests:
- we have to re-work how are test utility is structured
- we have to reduce tests