Changeset calculator between two states of a data
The bug #6 was fixed in this release, and the changeset computer was also a bit simplified.
This release fixes a bug on the null value handling.
If the new value was null, even if it was unchanged, modified or added, it was always considered as a Removal instead of an expected Modification, Addition or unchanged value.
This is due to the php's isset operator which considers that null does not set a value.
To enhance the possibilties to extend the Set class, its changes property is now protected instead of private
Quality fixes to make SensioLabsInsight happy. <3
New feature : more detailed changes on each changes. Now, instead of a Totem\ Change object (or Totem\ChangeInterface to be more precise), you'll get a Totem\AbstractChange), which can be one of the following :
Totem\Change\Addition if the data was added
Totem\Change\Modification if the data was modified
Totem\Change\Removal if the data was removed
Some enhancements were also brought up on the Snapshot parts, and the constraint on the ArraySnapshot (that each keys in two snapshots must be the same if you want to compare two arrays) is now gone.
ObjectSnapshot (ReflectionProperty was misused)AbstractSnapshot
Set (check only the object's hash)