gergely/taskwarrior-2.x
1
0
Fork 0
Code Issues Actions Packages Projects Releases 1 Wiki Activity

Control whether to renumber the working set when rebuilding it

Browse Source
This commit is contained in:
Dustin J. Mitchell
2021-01-02 14:40:05 -05:00
parent b62370c150
commit dc2df10158
8 changed files with 135 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
taskchampion/src/replica.rs
View File

@@ -170,12 +170,14 @@ impl Replica {
self.taskdb.sync(server)
}
/// Perform "garbage collection" on this replica. In particular, this renumbers the working
/// set to contain only pending tasks.
pub fn rebuild_working_set(&mut self) -> Fallible<()> {
/// Rebuild this replica's working set, based on whether tasks are pending or not. If
/// `renumber` is true, then existing tasks may be moved to new working-set indices; in any
/// case, on completion all pending tasks are in the working set and all non- pending tasks are
/// not.
pub fn rebuild_working_set(&mut self, renumber: bool) -> Fallible<()> {
let pending = String::from(Status::Pending.to_taskmap());
self.taskdb
.rebuild_working_set(|t| t.get("status") == Some(&pending))?;
.rebuild_working_set(|t| t.get("status") == Some(&pending), renumber)?;
Ok(())
}
}
@@ -251,7 +253,7 @@ mod tests {
assert_eq!(t.get_status(), Status::Deleted);
assert_eq!(t.get_description(), "gone");
rep.rebuild_working_set().unwrap();
rep.rebuild_working_set(true).unwrap();
assert!(rep.get_working_set_index(t.get_uuid()).unwrap().is_none());
}