Brick\Money VS date-time

For the last couple of years I’ve been using Value Objects in my projects to bring language-level strict types to what would typically be array data structures in my code. From method inputs to JSON API responses, value objects have almost entirely replaced arrays throughout. The ability to get runtime type checking and IDE auto-complete has eliminated many potential bugs, from key typos, to assigning an incorrectly typed value by accident: what type is an “amount” property in a credit card transaction API response? An integer of cents (or other minor units), a Money object such as brick/money or moneyphp/money? Or worst of all, a float?

brick/money: A money and currency library for PHP

1 - Floating point is not always great for money operations and can introduce odd rounding errors - https://www.php.net/manual/en/language.types.float.php - you might want to use something like this: https://github.com/brick/money

He should have said to use Brick/Money https://github.com/brick/money which is based on Brick/Math but is specifically money related.

If you don’t want to do the integer conversions yourself, I highly recommend looking at: https://github.com/brick/money

brick/date-time is great! I personally prefer its interface and functionality over Carbon's. I also really like his money library

Is the most popular, but https://github.com/brick/money is preferrable IMO. One of the reasons is that it handles not just money, but all arbitrary precision calculations independent of currecy via brick/math.

brick/date-time: Date and time library for PHP

brick/date-time: Date and time library for PHP

If you're happy to bring in another library, you could replace your Date VO class with the LocalDate class from the brick/datetime library. It does the same thing, just has three int fields inside instead of a string in Y-m-d format.

If you need to store subsets of a date-time-timezone combination, then take a look at brick/date-time instead.

Slightly related but https://github.com/brick/date-time is a wonderful library to manage datetime concepts in a proper way.

Looks like a CivilDate is the same thing that brick/date-time calls a LocalDateTime. Does this library have any advantages over the one from Brick?

I like https://github.com/brick/date-time

It is a good practice to use an interface to manage the clock in an application, as it allows having full control of time. For example, it eases testing, as it lets us define the concrete time for each test. Frank de Jonge and Matthias Noback have blog posts about it, brick has an implementation, and there is even a PSR proposal to have a ClockInterface.