detectRemoteDeletions property
Whether a full pull should treat entities that exist locally but are absent remotely as remote deletions, routing each through the conflict resolver (as a DatumConflictType.deletionConflict with a null remote).
Defaults to false (previous behavior: remote deletions were invisible during pull). When enabled, detection runs only on a full pull (no scope and no query filter — a filtered pull legitimately returns a subset) and skips entities with pending local operations or already soft-deleted locally. The default LastWriteWinsResolver keeps local data (safe); use a remote-priority resolver to actually propagate deletions.
Implementation
final bool detectRemoteDeletions;