date-time VS calendar

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.

https://github.com/aeon-php/calendar comes with object representation of TimeUnit, more advanced iterators over TimePeriods, time ranges and overlaps detection, leap seconds support, Unix/UTC/TAI/GPS timestamps plus few handy extensions like holidays, business hours, retries, precise sleep, stopwatch, rate limiter. It’s a wrapper on an excellent native DateTime that does not extend it.

Hey, We are planning to release version 1.0 with long term support of https://github.com/aeon-php/calendar library and we thought it's a good time to ask for some feedback. How this library is different from other great libraries available in the wild? The main difference is that it does not extend \DateTime or \DateTimeImmutable, but instead it provides own fully immutable DateTime replacement. Why? There are few reasons but the most important one is to provide better and safer, Object Oriented API to work with DateTime/Date/Time/TimeZone/TimeUnit and TimePeriods. Safer means that the whole library API is designed to expose commonly misunderstood concepts and make them explicit, like for example adding month to given date expects to precisely define number of days DateTime::add(TimeUnit::days(30)); as a TimeUnit instance or use relative time unit DateTime::add(RelativeTimeUnit::month()); Calendar is the core library and it comes with few extra things like support for LeapSeconds, different Time Epoch (TAI, GPS), TimePeriods (iterating, overlapping, merging, finding gaps, sorting etc) or precise time measurement. There are few more libraries built on top of calendar, like for example Business Hours, Holidays (which is just an abstraction and bridge for other libraries), Rate Limiter, Retry but they all waits for the the calendar to be stabilized. You can find them here https://github.com/aeon-php