Skip to content

Compares of Java Collections and Objects (of different classes) made easy

License

Notifications You must be signed in to change notification settings

nejckorasa/compare-utils

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

45 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Compare Utils

Download Codacy Badge Build Status Tweet

Intro

Compares of Java Collections and Objects made easy.

It provides easy way to compare Java Collections and Java Objects of same or different class when Java's equals functions and Java's Comparators don't suffice and you want to compare objects differently.

Compare result of collections is presented with clear separation of added, removed, updated and unchanged items.

Install

Using Maven simple add following dependency:

<dependency>
  <groupId>io.github.nejckorasa</groupId>
  <artifactId>compare-utils-core</artifactId>
  <version>1.0.2-RELEASE</version>
</dependency>

or with Gradle:

compile 'io.github.nejckorasa:compare-utils:1.0.2-RELEASE'

Docs

Javadoc documentation is provided

Features

At first glance it might seem that this is no different than using Java's own Comparator and even Java's equals functions. For some cases it is indeed easier to use Comparator and you should!

A few examples where using this library is useful:

  • Compare collections of different object classes

    • Specify keyExtractor and your own equals function
    • Instead of writing equals function, you can compare objects by comparing only some of it's fields. See example below and equalities or equalityPairs definitions in Comparing.
  • Compare objects (of same or different class) by comparing only some of it's fields

    • All you need to do is list field extractors, see example below.
Class1 {
    long id;
    int firstProperty;
    String secondProperty;
    ...
}

Class2 {
    long id;
    int propertyOne;
    String propertyTwo;
    ...
}

// Compare collections of different classes by only comparing 2 of their fields and matching by id

CollectionCmp
    .ofDifferent(class1List, class2List)
    .withEqualityPairs(Arrays.asList(
        EqualityPair.of(o1 -> o1.getFirstProperty(), o2 -> o2.getPropertyOne()),
        EqualityPair.of(o1 -> o1.getSecondProperty(), o2 -> o2.getPropertyTwo()))) // equalityPairs
    .compare(item -> item.getId()); // keyExtractor
    
// Compare objects of different classes by only comparing 2 of their fields

ObjectCmp.equalEqualityPairs(
  class1Object,
  class2Object,
  Arrays.asList(
      EqualityPair.of(o1 -> o1.getFirstProperty(), o2 -> o2.getPropertyOne()),
      EqualityPair.of(o1 -> o1.getSecondProperty(), o2 -> o2.getPropertyTwo())));

Tests also include some examples that you might find useful.

Collections compare

Basics

It provides comparing and finding differences between two collection - base and working collection. Items in collections can be of same or different classes, both are supported. Two steps are important to understand how comparison is made and differences are found:

  1. Matching

    First, items from both collections are matched together by their keys. Each item is assigned it's own key. Keys are computed using provided keyExtractor functions. When 2 items match they form a Pair.

  2. Comparing

    Each pair is compared using provided equalsFunction, equalities or equalityPairs.

Matching

Matching is computed using keyExtractor functions. For example:

CollectionCmp
        .ofSame(baseList, workingList)
        .compare(item -> item.getId()); // keyExtractor function

or when comparing collections of different item classes:

CollectionCmp
        .ofDifferent(baseList, workingList)
        .compare(baseItem -> baseItem.getId(), workingItem -> workingItem.getId()); // keyExtractor functions for base and working items

keyExtractors are not optional and must always be provided.

Comparing

Comparing is performed on items that are matched together (they form a Pair). This is done by equalsFunction that can be defined in a few different ways:

equalsFunction

CollectionCmp
        .ofSame(baseList, workingList)
        .withEquals((item1, item2) -> item1.getName().equals(item2.getName())) // equalsFunction
        .compare(item -> item.getId()); // keyExtractor

equalities or equalityPairs

CollectionCmp
        .ofSame(baseList, workingList)
        .withEqualities(Arrays.asList(
          item -> item.getName(), 
          item -> item.getCode(), 
          item -> item.getDescription())) // equalities
        .compare(item -> item.getId()); // keyExtractor

In example above, items are considered equal when name, code and description fields are equal. Similarly with collections of different classes, equalityPairs are used:

CollectionCmp
        .ofDifferent(baseList, workingList)
        .withEqualityPairs(Arrays.asList(
            EqualityPair.of(baseItem -> baseItem.getName(), workingItem -> workingItem.getData().getName()),
            EqualityPair.of(baseItem -> baseItem.getCode(), workingItem -> workingItem.getData().getCode()))) // equalityPairs
        .compare(item -> item.getId()); // keyExtractor

Now, items are considered equal when name, code properties are equal. Because base and working items are not of same class, properties may exist on different paths.

equalsFunction is optional, if nothing is provided, Objects.equals() is used to compare matched items.

Result

Compare result of collections is presented with clear separation of added, removed, updated and unchanged items. Result object has a few useful functions to help you analyze result data:

CmpResult<O, O> compareResult = CollectionCmp
        .ofSame(baseList, workingList)
        .withEquality(item -> item.getName())
        .compare(item -> item.getId()); // keyExtractor

boolean hasChanges = compareResult.hasChanges();
int changesCount = compareResult.getChangesCount();

// different items are added and removed items ...
boolean hasDifferences = compareResult.hasDifferences();
int differentCount = compareResult.getDifferentCount();

compareResult.getAll();
compareResult.getAdded();
compareResult.getUdpated();
...

// changed items are added and removed or updated items ...
compareResult.getChanged();
compareResult.getUncanged();

// stream through changed, unchanged, added, different items ...
compareResult.streamChanged()
        .map( ... )
        ...

All result data is provided in Pairs, containing matched base and working item as well as difference type:

CmpPair<B, W> pair = ...

B base = pair.getBase();
W working = pair.getWorking();

Diff diff = pair.getDiff(); // UNCHANGED, UPDATED, ADDED, REMOVED
Serializable key = pair.getKey(); // key by which items are matched together

Partitioning

Matching must be a injective function (in both ways) == there must be at most one item with the same key in each collection. If that condition is not met, collection cannot be partitioned and collections compare result might not be correct.

You can check if collection can be partitioned using:

boolean canPartition = CollectionCmpPartitioner.canPartition(collection, keyExtractor)

Objects compare

Objects are compared using same features as comparing in collections above (see Comparing), for example:

// check if objects are equal based on it's name, code and description
boolean equals = ObjectCmp.equalEqualities(
    object1, 
    object2, 
    Arrays.asList(o -> o.getName(), o -> o.getCode(), o -> o.getDescription())));

Contributing

Pull requests are welcome, Show your ❤ with a ★