Class ApplyOptions

atomic-core/src/crdt/apply/options.rs:88–144

/// ```
#[derive(Debug, Clone, PartialEq, Eq, Serialize, Deserialize)]
pub struct ApplyOptions {
    /// Whether to validate CRDT ordering constraints.
    ///
    /// When enabled, the apply process verifies that insertions respect
    /// the CRDT ordering invariants (e.g., "after" references are valid).
    validate_ordering: bool,

    /// Whether to validate that referenced entities exist.
    ///
    /// When enabled, the apply process verifies that all referenced
    /// TrunkIds, BranchIds, and LeafIds exist before operating on them.
    validate_references: bool,

    /// Whether to track detected conflicts.
    ///
    /// When enabled, conflicts are recorded in the [`ApplyContext`] for
    /// later inspection. This allows the caller to decide how to handle them.
    ///
    /// [`ApplyContext`]: super::context::ApplyContext
    track_conflicts: bool,

    /// Whether to fail immediately on conflict detection.
    ///
    /// When enabled, the first detected conflict causes the apply to fail.
    /// When disabled, conflicts are tracked (if `track_conflicts` is true)
    /// and the apply continues.
    fail_on_conflict: bool,

    /// Whether to allow duplicate CRDT IDs.
    ///
    /// When enabled, operations with IDs that already exist are silently
    /// skipped (idempotent behavior). When disabled, duplicate IDs cause
    /// an error.
    ///
    /// This is useful for recovery scenarios where changes might be
    /// partially applied.
    allow_duplicate_ids: bool,

    /// Whether to update reverse index tables.
    ///
    /// When enabled, reverse lookup tables (PATH_TRUNK, INODE_TRUNK) are
    /// updated during apply. Disabling this can improve performance but
    /// requires a separate index rebuild.
    update_reverse_indexes: bool,

    /// Maximum number of operations to apply.
    ///
    /// When set, the apply process stops after this many operations.
    /// This can be used for batched processing or to limit resource usage.
    max_operations: Option<usize>,

    /// Whether to verify content ranges are valid.
    ///
    /// When enabled, content byte ranges are verified against the actual
    /// content blob length.
    validate_content_ranges: bool,
}