✨ Adds option to ignore revision records with same old and new values ​​in Revisionable Trait

[phpiando]

Addition of a new revisionIgnoreSameValue property:

This property is a boolean flag that allows you to enable or disable the functionality of ignoring revisions where the old value is equal to the new one. By default, this functionality is disabled (false).

Implementation of the ignoreRevisionSameValue($oldValue, $newValue) method:

This method checks whether the revisionIgnoreSameValue property is enabled and, if so, returns true when the old value is equal to the new value, thus skipping the creation of the revision record.

Adjustment to revision creation logic in the revisionableAfterUpdate() method:

Added a check to call the ignoreRevisionSameValue method before adding a revision record.

Justification for Changes:

• Optimization of Revision Records: By avoiding the creation of unnecessary revisions when values ​​do not change, the storage of revisions becomes more efficient and less polluted.
• Flexibility: The new revisionIgnoreSameValue property allows developers to optionally control this functionality, which can be enabled or disabled according to the needs of the project.

Additional Notes:

Testing has been performed to ensure that the default behavior of the Revisionable trait has not changed and that revisions are still recorded correctly when this new functionality is disabled.
It is recommended that you review the documentation for additional information about this new option.

Checklist:

• Code follows the project's style standards.
• Tests have been added or updated to cover the new functionality.
• Documentation has been updated as needed.

[bennothommo]

Hi @phpiando - thanks for submitting this PR.

My understanding is that this trait already checks if revisionable fields have been changed or not from this line:

storm/src/Database/Traits/Revisionable.php

Line 75 in b5f971f

$dirty = $this->getDirty();

. The getDirty() method should only return fields that have been changed, so your additional check would be redundant at that point.

Do you have an example of the Revisionable trait saving unchanged data in a new revision?