v4.5.0

Changes:

• refactor: remove 'abstract' access modifier from VOs

Notes:

Before: you must create a child VO class that extend VO class
After: you can use parent VO (Ex: StringValueObject) without create child class

v4.4.0

feat: add equivalentTo function to collection value object

function is similar to equalTo, but:

• equalTo: two identical collections with different order returned false.
• equivalentTo: two equal collections with different order return true.

v4.3.1

fix: remove impossible return type cases

v4.3.0

• feat: override all date time factory functions

v4.2.1

fix: prevent generate not UTC datetime

This value object was thinking for use UTC as TimeZone standar. However, it allow set other timezone by passing it on "from" factory:

$date = DateTimeValueObject::from('2025-01-10T15:16:11+01:00')

echo $date->format(\DATE_ATOM) ; // result 2025-01-10T15:16:11+01:00

Before this fix, date was transformed to UTC, expected result: 2025-01-10T14:16:11+00:00

v4.2.0

• Add date value object #40
• Renamed DateTimeRangeValeObject to DateTimeRangeValueObject and deprecated the first.
• Added value method to Value interface

v4.1.0

feat: Add unique id value object

v4.0.1

• fix: Keep microseconds in DateTimeValueObject #38

v4.0.0

• feat: allow set occurred on datetime format
• refactor: remove aggregate message aggregate uuid support
• refactor: add static return types to factories

v3.1.0

• AggregateMessage edited: now aggregate id is a string value object, not uuid required.
• Add deprecation: on "AggregateMessage::fromPayload" $aggregateId should be a AggregateId value object instead of Uuid.