changes#

Change sets for a live Project. SchedulingChanges is the edit set that Project::apply, Project::preview and each Project::evaluate candidate take. Project::suggest_assignments returns one in its proposal. The folder also holds the per-kind Changes bucket, the add and update records, Patch for partial field edits, and ApplyReport with its parts. Everything is re-exported at the crate root, so you import plen_core::SchedulingChanges, not an internal module path.

• AppliedOperationOne accepted operation of a change set, identified by its path
• ApplyReportOutcome of Project::apply - accepted and rejected operations, side effects and the resync flag
• AssignmentUpdatePartial edit of one existing assignment in a live project
• ChangeEffectsIds that an applied change set removed, generated or dropped beyond the operations it named
• ChangesThe add, update and remove lists for one kind of record in a change set
• LinkAddA new link in a change set, with an optional id that the engine generates when omitted
• LinkUpdateA partial edit of one existing link in a live project
• PatchThree-state field of update records - leave unchanged, clear, or set
• RejectedOperationOne operation of a change set that wasn't applied, with its path and the reason
• ResourceUpdateAn edit to an existing resource's capacity or calendar
• SchedulingChangesOne set of edits to a live project, grouped into task, link, resource and assignment buckets, with an optional baseline check
• TaskUpdateEdit to an existing task - only the fields you set change