Bug fixes on the Set (Part 2)

The bug #6 was fixed in this release, and the changeset computer was also a bit simplified.

Bug fixes on the Set

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.

Fix bad visibility for Set class

To enhance the possibilties to extend the Set class, its changes property is now protected instead of private

Quality

Quality fixes to make SensioLabsInsight happy. <3

v1.2.0

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.

Deep Snapshots

• #1, #4 : Snapshots are now deeply calculated
• Basic usage docs

Bug fixes on object snapshot

• Fixes #3 : Fixes a bug on ObjectSnapshot (ReflectionProperty was misused)
• Enhance code coverage
• Removed useless time verification in AbstractSnapshot
• Simplified object comparision in Set (check only the object's hash)

First release

v1.0.0

Add ArraySnapshot

Development Release

v0.4

Alter README file