backbone-events 0.3.30

Events core + the sale/booth/crm/sms/desk overlay — registrations under one authoritative seat counter, the sale seam (order-minted registrations, forward-only paid heal, SO-cancel mirror cascade), booth bookings with the DB exclusivity wall, closed-vocabulary lead rules through a host sink port, the dual-channel (mail/sms) self-arming scheduler, and the exact-match desk verb (Odoo event port, core + overlay)
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

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

use backbone_core::GenericCrudService;

use crate::presentation::dto::{CreateLeadProvenanceDto, UpdateLeadProvenanceDto};
use crate::domain::entity::LeadProvenance;
use crate::infrastructure::persistence::LeadProvenanceRepository;

/// Application service for LeadProvenance 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 `lead_provenance_service_custom.rs`:
///
/// ```rust,ignore
/// pub struct LeadProvenanceServiceCustom {
///     inner: Arc<LeadProvenanceService>,
///     // add domain-specific dependencies here
/// }
/// ```
pub type LeadProvenanceService = GenericCrudService<
    LeadProvenance,
    CreateLeadProvenanceDto,
    UpdateLeadProvenanceDto,
    LeadProvenanceRepository,
>;

// <<< CUSTOM
// END CUSTOM