MCPcopy Create free account
hub / github.com/atomicdotdev/atomic / include_deleted_edges

Method include_deleted_edges

atomic-core/src/output/alive/retrieve/options.rs:201–203  ·  view source on GitHub ↗

Whether `iter_forward` should include deleted edges. When a change filter is active, we always include deleted edges because we need to traverse them to find content that was deleted by changes OUTSIDE our filter (which means the content was still alive at the target state). Same when `include_deleted` is explicitly set.

(&self)

Source from the content-addressed store, hash-verified

199 /// alive at the target state). Same when `include_deleted` is
200 /// explicitly set.
201 pub(crate) fn include_deleted_edges(&self) -> bool {
202 self.include_deleted || self.change_filter.is_some() || self.deletions_final
203 }
204
205 // ------------------------------------------------------------------
206 // Typed edge model — Phase A3 replacements

Callers 1

retrieve_graphFunction · 0.80

Calls

no outgoing calls

Tested by

no test coverage detected