Package org.javers.core.diff.custom
Class NullAsBlankStringComparator
java.lang.Object
org.javers.core.diff.custom.NullAsBlankStringComparator
- All Implemented Interfaces:
CustomValueComparator<String>
Compares Strings treating blank and null strings as equal.
Usage example:
Usage example:
JaversBuilder.javers()
.registerValue(String.class, new NullAsBlankStringComparator())
.build();
-
Constructor Summary
Constructors -
Method Summary
-
Constructor Details
-
NullAsBlankStringComparator
public NullAsBlankStringComparator()
-
-
Method Details
-
equals
Description copied from interface:CustomValueComparatorCalled by Javers to compare two Values.- Specified by:
equalsin interfaceCustomValueComparator<String>- Parameters:
a- not null ifCustomValueComparator.handlesNulls()returns falseb- not null ifCustomValueComparator.handlesNulls()returns false
-
toString
Description copied from interface:CustomValueComparatorThis method has two roles. First, it is used when Values are compared in hashing contexts. Second, it is used to build Entity Ids from Values.
Hashcode role
When a Value class has customtoString(), it is used instead ofObject.hashCode()when comparing Values in hashing contexts, so:- Sets with Values
- Lists with Values compared as
ListCompareAlgorithm.AS_SET - Maps with Values as keys
toString()implementation should be aligned with customCustomValueComparator.equals(Object, Object)in the same way likeObject.hashCode()should be aligned withObject.equals(Object).
Entity Id role
Each Value can serve as an Entity Id.
When a Value has customtoString()function, it is used for creatingInstanceIdfor Entities. If a Value doesn't have a customtoString(), defaultReflectionUtil.reflectiveToString(Object)) is used.
See full example CustomToStringExample.groovy.- Specified by:
toStringin interfaceCustomValueComparator<String>- Parameters:
value- not null ifCustomValueComparator.handlesNulls()returns false
-
handlesNulls
public boolean handlesNulls()Description copied from interface:CustomValueComparatorThis flag is used to indicate to Javers whether a comparator implementation wants to handle nulls.
By default, the flag is false and Javers checks if both values are non-null before calling a comparator.
If any of given values is null — Javers compares them using the standard Java logic:- null == null
- null != non-null
If the flag is true — Javers skips that logic and allows a comparator to handle nulls on its own. In that case, a comparator holds responsibility for null-safety.- Specified by:
handlesNullsin interfaceCustomValueComparator<String>- See Also:
-