Collection merger library.
License
—
Deps
0
Install Size
—
Vulns
✓ 0
Published
Jan 6, 2026
$ dotnet add package CollectionMergerSynchronize/merge collections while generating a change report (added/updated/removed), including nested collection merges.
net8.0, net9.0, net10.0CollectionSyncExtensions.MapFrom(...)SyncReport with a list of ChangeRecord itemsSee CHANGELOG.md for release history.
dotnet add package CollectionMerger
Install-Package CollectionMerger
<PackageReference Include="CollectionMerger" Version="x.y.z" />
You merge a source collection into a destination collection by providing:
matchPredicate: how to match a source item to an existing destination item (usually by an ID)mapProperties: how to copy/update properties from source to destinationusing CollectionMerger;
var destination = new List<Person>
{
new() { Id = 1, Name = "Alice" },
new() { Id = 2, Name = "Bob" }
};
var source = new List<PersonDto>
{
new() { Id = 1, Name = "Alice Updated" },
new() { Id = 3, Name = "Charlie" }
};
var report = destination.MapFrom(
source: source,
matchPredicate: (src, dest) => src.Id == dest.Id,
mapProperties: (src, dest, _m) =>
{
dest.Id = src.Id;
dest.Name = src.Name;
});
Console.WriteLine($"Added: {report.AddedCount}, Updated: {report.UpdatedCount}, Removed: {report.RemovedCount}");
For nested collections, call MapFrom(...) on the child collection and pass the parent Mapper so paths get nested.
using CollectionMerger;
var report = destinationPeople.MapFrom(
source: sourcePeople,
matchPredicate: (srcPerson, destPerson) => srcPerson.ID == destPerson.ID,
mapProperties: (srcPerson, destPerson, m1) =>
{
destPerson.ID = srcPerson.ID;
destPerson.Name = srcPerson.Name;
destPerson.Cats.MapFrom(
parent: m1,
source: srcPerson.Cats,
matchPredicate: (srcCat, destCat) => srcCat.ID == destCat.ID,
mapProperties: (srcCat, destCat, _m2) =>
{
destCat.ID = srcCat.ID;
destCat.Name = srcCat.Name;
});
});foreach (var change in report.Changes)
{
Console.WriteLine($"{change.ChangeType}: {change.Path}");
if (change.PropertyChanges is null)
continue;
foreach (var prop in change.PropertyChanges)
Console.WriteLine($" - {prop.PropertyName}: '{prop.OldValue}' -> '{prop.NewValue}'");
}SyncReport.Changes contains ChangeRecord entries:
ChangeType: Added, Updated, or RemovedPath: a stable-ish path for the item (supports nesting)Item: the destination item instancePropertyChanges: only present for UpdatedPaths look like Person[1] and Person[1].Cat[3].
The [...] value is chosen by looking for a public readable ID or Id property on either the source or destination item. If neither exists, it becomes ?.
After your mapProperties delegate runs, CollectionMerger snapshots public instance scalar properties (excluding enumerables except string) and records an Updated change if any of those values differ.
No. Collection properties are ignored for property change detection.
If you want nested changes, perform nested merges with the nested overload of MapFrom(...).
ICollection<TDestination>TDestination must have a parameterless constructor (new() constraint)matchPredicate (make sure it uniquely identifies items)If you hit a bug or want to request a feature, please open an issue: https://github.com/alexdresko/collection-merger/issues
Releases are automated via Release Please.
main using Conventional Commits.CHANGELOG.md and package version.The release workflow expects a GitHub Actions secret:
NUGET_API_KEY (or NUGET_TOKEN): a NuGet.org API key with permission to push packages.