[Canonical page](<https://docs.dhtmlx.com/planning-engine/rust/api/core/changes/overview/>)
[Full documentation index](<https://docs.dhtmlx.com/planning-engine/llms.txt>)


# changes

Change sets for a live [`Project`](<https://docs.dhtmlx.com/planning-engine/rust/api/core/project/project.md>). [`SchedulingChanges`](<https://docs.dhtmlx.com/planning-engine/rust/api/core/changes/scheduling-changes.md>) 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`](<https://docs.dhtmlx.com/planning-engine/rust/api/core/changes/changes.md>) bucket, the add and update records, [`Patch`](<https://docs.dhtmlx.com/planning-engine/rust/api/core/changes/patch.md>) for partial field edits, and [`ApplyReport`](<https://docs.dhtmlx.com/planning-engine/rust/api/core/changes/apply-report.md>) with its parts. Everything is re-exported at the crate root, so you import `plen_core::SchedulingChanges`, not an internal module path.

:::category-index
:::