backbone-mail 0.6.0

Odoo mail core port — message/notification/followers/activity/alias/sms queue (schema: messaging)
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 FetchmailServer entities
//!
//! Generated by metaphor-schema. Do not edit manually.
//!
//! Type alias over `GenericCrudService` — all CRUD logic lives in backbone-core.
//! For custom behaviour, create `fetchmail_server_service_custom.rs` (preserved on regen).

use backbone_core::GenericCrudService;

use crate::presentation::dto::{CreateFetchmailServerDto, UpdateFetchmailServerDto};
use crate::domain::entity::FetchmailServer;
use crate::infrastructure::persistence::FetchmailServerRepository;

/// Application service for FetchmailServer 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 `fetchmail_server_service_custom.rs`:
///
/// ```rust,ignore
/// pub struct FetchmailServerServiceCustom {
///     inner: Arc<FetchmailServerService>,
///     // add domain-specific dependencies here
/// }
/// ```
pub type FetchmailServerService = GenericCrudService<
    FetchmailServer,
    CreateFetchmailServerDto,
    UpdateFetchmailServerDto,
    FetchmailServerRepository,
>;

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

#[async_trait::async_trait]
impl backbone_core::write_guard::WriteGuard<FetchmailServer> for FetchmailServerRowRules {
    async fn check(
        &self,
        ctx: &backbone_core::write_guard::WriteCtx<'_, FetchmailServer>,
    ) -> 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();
        // `name_required` (@required on FetchmailServer.name)
        if (create || (update && r::changed(old.as_ref(), row, &["name"]))) && !r::holds(&r::and(r::is_not_null(r::field(row, "name")), r::not(r::is_empty(r::trim(r::field(row, "name")))))) {
            refuse.push(Violation::new("name", "required", "name is required"));
        }
        // `token_hash_required` (@required on FetchmailServer.token_hash)
        if (create || (update && r::changed(old.as_ref(), row, &["token_hash"]))) && !r::holds(&r::and(r::is_not_null(r::field(row, "token_hash")), r::not(r::is_empty(r::trim(r::field(row, "token_hash")))))) {
            refuse.push(Violation::new("token_hash", "required", "token_hash is required"));
        }
        GuardOutcome { refuse, shadow }
    }
}