Chronos aims to be a drop-in replacement for nesbot/carbon. It focuses on providing
immutable date/datetime objects. Immutable objects help ensure that datetime objects
aren't accidentally modified keeping data more predictable.
Installing with composer:
$ composer require cakephp/chronos
You can then use Chronos:
<?php
require 'vendor/autoload.php';
use Cake\Chronos\Chronos;
printf("Now: %s", Chronos::now());The biggest and main difference is that Chronos extends DateTimeImmutable instead of DateTime.
Immutability for date values has proven to be a great way of avoiding bugs and reduce the amount of code,
since developers don't have to manually copy the instance every time they need a change.
Another important feature it offers is the Date class, which is used for representing dates without time (calendar dates).
Any time method called on this type of object is basically a no-op.
A minor but still noticeable difference is that Chronos has no external dependencies, it is completely standalone.
Finally, Chronos is faster than Carbon as it has been optimized for the creation of hundreds of instances with minimal overhead.
Chronos also strives for HHVM compatibility, this library can be used safely with HHVM 3.11.
First add cakephp/chronos to your composer.json:
php composer.phar require cakephp/chronosBy default Chronos includes a compatibility script that creates aliases for the
relevant Carbon classes. This will let most applications upgrade with very
little effort. If you'd like to permanently update your code, you will
need to update imports and typehints. Assuming src contains the files you
want to migrate, we could use the following to update files:
# Replace imports
find ./src -type f -exec sed -i '' 's/use Carbon\\CarbonInterval/use Cake\\Chronos\\ChronosInterval/g' {} \;
find ./src -type f -exec sed -i '' 's/use Carbon\\Carbon/use Cake\\Chronos\\Chronos/g' {} \;
# Replace typehints and extensions
find ./src -type f -exec sed -i '' 's/CarbonInterval/ChronosInterval/g' {} \;
find ./src -type f -exec sed -i '' 's/Carbon/Chronos/g' {} \;
At this point your code should mostly work as it did before. The biggest different is that Chronos instances are immutable.
Immutable objects have a number of advantages:
- Using immutable objects is always free of side-effects.
- Dates and times don't accidentally change underneath other parts of your code.
With those benefits in mind, there are a few things you need to keep in mind when modifying immutable objects:
// This will lose modifications
$date = new Chronos('2015-10-21 16:29:00');
$date->modify('+2 hours');
// This will keep modifications
$date = new Chronos('2015-10-21 16:29:00');
$date = $date->modify('+2 hours');In the case that you need a mutable instance you can get one:
$time = new Chronos('2015-10-21 16:29:00');
$mutable = $time->toMutable();
$date = new Date('2015-10-21');
$mutable = $date->toMutable();If you have a mutable object and want an immutable variant you can do the following:
$time = new MutableDateTime('2015-10-21 16:29:00');
$fixed = $time->toImmutable();
$date = new MutableDate('2015-10-21');
$fixed = $date->toImmutable();PHP only offers datetime objects as part of the native extensions. Chronos
adds a number of conveniences to the traditional DateTime object and introduces
a Date object. Date instances offer compatibility with the ChronosInterface, but
have their time & timezone frozen to 00:00:00 UTC. This makes them ideal when working with
calendar dates as the time components will always match.
use Cake\Chronos\Date;
$today = new Date();
echo $today;
// Outputs '2015-10-21'
echo $today->modify('+3 hours');
// Outputs '2015-10-21'Like instances of Chronos, Date objects are also immutable. The MutableDate class provides
a mutable variant of Date.
A more descriptive documentation can be found at book.cakephp.org/3.0/en/chronos.html.
API documentation can be found on api.cakephp.org/chronos.