backbone-mailing 0.9.0

Email marketing — mass-mail engine: audiences, subscriptions, hand-set mailing lifecycle, seeded A/B testing, per-recipient traces, cycle-44 bridge targets (Odoo mass_mailing port)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72

//! Application service for MailingSubscription entities
//!
//! Generated by metaphor-schema. Do not edit manually.
//!
//! Type alias over `GenericCrudService` — all CRUD logic lives in backbone-core.
//! For custom behaviour, create `mailing_subscription_service_custom.rs` (preserved on regen).

use backbone_core::GenericCrudService;

use crate::presentation::dto::{CreateMailingSubscriptionDto, UpdateMailingSubscriptionDto};
use crate::domain::entity::MailingSubscription;
use crate::infrastructure::persistence::MailingSubscriptionRepository;

/// Application service for MailingSubscription entities.
///
/// All 12 standard CRUD operations (list, create, get, update, patch,
/// soft_delete, restore, empty_trash, bulk_create, upsert, find_by_id,
/// list_deleted) are provided by `GenericCrudService`.
///
/// Custom extensions go in `mailing_subscription_service_custom.rs`:
///
/// ```rust,ignore
/// pub struct MailingSubscriptionServiceCustom {
///     inner: Arc<MailingSubscriptionService>,
///     // add domain-specific dependencies here
/// }
/// ```
pub type MailingSubscriptionService = GenericCrudService<
    MailingSubscription,
    CreateMailingSubscriptionDto,
    UpdateMailingSubscriptionDto,
    MailingSubscriptionRepository,
>;

/// The rules the schema declares for MailingSubscription, checked against the row a create or update
/// would store. The generated build attaches it to [`MailingSubscriptionService`]. A refusing rule's
/// break answers 422; a rule in shadow is logged under `backbone::write_guard` and the
/// write goes ahead.
pub struct MailingSubscriptionRowRules;

#[async_trait::async_trait]
impl backbone_core::write_guard::WriteGuard<MailingSubscription> for MailingSubscriptionRowRules {
    async fn check(
        &self,
        ctx: &backbone_core::write_guard::WriteCtx<'_, MailingSubscription>,
    ) -> backbone_core::write_guard::GuardOutcome {
        use backbone_core::row_rule as r;
        use backbone_core::violation::Violation;
        use backbone_core::write_guard::{GuardOutcome, WriteKind};
        let (create, update) = (ctx.kind == WriteKind::Create, ctx.kind == WriteKind::Update);
        let Some(after) = ctx.after.filter(|_| create || update) else {
            return GuardOutcome::allow();
        };
        let Ok(row) = serde_json::to_value(after) else {
            return GuardOutcome::allow();
        };
        let row = &row;
        let old = ctx.before.and_then(|b| serde_json::to_value(b).ok());
        let shadow = Vec::new();
        let mut refuse = Vec::new();
        // `contact_id_required` (@required on MailingSubscription.contact_id)
        if (create || (update && r::changed(old.as_ref(), row, &["contact_id"]))) && !r::holds(&r::and(r::is_not_null(r::field(row, "contact_id")), r::not(r::is_empty(r::trim(r::field(row, "contact_id")))))) {
            refuse.push(Violation::new("contact_id", "required", "contact_id is required"));
        }
        // `mailing_audience_id_required` (@required on MailingSubscription.mailing_audience_id)
        if (create || (update && r::changed(old.as_ref(), row, &["mailing_audience_id"]))) && !r::holds(&r::and(r::is_not_null(r::field(row, "mailing_audience_id")), r::not(r::is_empty(r::trim(r::field(row, "mailing_audience_id")))))) {
            refuse.push(Violation::new("mailing_audience_id", "required", "mailing_audience_id is required"));
        }
        GuardOutcome { refuse, shadow }
    }
}