Download the PHP package solodkiy/brick-date-time without Composer

Brick\DateTime (solodkiy fork)

A powerful set of immutable classes to work with dates and times.

Introduction

This library builds an extensive API on top of the native PHP date-time classes, and adds missing concepts such as LocalDate, LocalTime, YearMonth, MonthDay, etc.

The classes follow the ISO 8601 standard for representing date and time concepts.

This component follows an important part of the JSR 310 (Date and Time API) specification from Java. Don't expect an exact match of class and method names though, as a number of differences exist for technical or practical reasons.

All the classes are immutable, they can be safely passed around without being affected.

Installation

This library is installable via Composer:

Requirements

This library requires PHP 8.1 or later.

About this fork

While this library is still under development, it is well tested and should be stable enough to use in production environments.

New functional

• new UtcDateTime class
• Instant::toUtcDateTime() method
• LocalDateTime::fromSqlFormat() method
• LocalDateTime::toSqlFormat() method
• ZonedDateTime::fromSqlFormat() method
• ZonedDateTime::toSqlFormat() method
• ZonedDateTime::toUtcDateTime() method
• ZonedDateTime::toNativeFormat() method
• ZonedDateTime::toUtcSqlFormat() method

Compatibility with brick/date-time

Overview

Main classes

The following classes/enums represent the date-time concepts:

• DayOfWeek: a day-of-week such as Monday (enum)
• Duration: a duration measured in seconds and nanoseconds
• Instant: a point in time, with a nanosecond precision
• Interval: a period of time between two instants
• LocalDate: an isolated date such as 2014-08-31
• LocalDateRange: an inclusive range of local dates, such as 2014-01-01/2014-12-31
• LocalDateTime: a date-time without a time-zone, such as 2014-08-31T10:15:30
• LocalTime: an isolated time such as 10:15:30
• Month: a month-of-year such as January (enum)
• MonthDay: a combination of a month and a day, without a year, such as --12-31
• Period: a date-based amount of time, such as '2 years, 3 months and 4 days'
• TimeZoneOffset: an offset-based time-zone, such as +01:00
• TimeZoneRegion: a region-based time-zone, such as Europe/London
• Year: a year in the proleptic calendar
• YearMonth: a combination of a year and a month, such as 2014-08
• ZonedDateTime: a date-time with a time-zone, such as 2014-08-31T10:15:30+01:00. This class is conceptually equivalent to the native DateTime class
• UtcDateTime: a date-time with a UTC time-zone, such as 2014-08-31T10:15:30Z. This class is sub-class of ZonedDateTime

These classes belong to the Brick\DateTime namespace.

Clocks

All objects read the current time from a Clock implementation. The following implementations are available:

• SystemClock returns the system time; it's the default clock
• FixedClock: returns a pre-configured time
• OffsetClock: adds an offset to another clock
• ScaleClock: makes another clock fast-forward by a scale factor

These classes belong to the Brick\DateTime\Clock namespace.

In your application, you will most likely never touch the defaults, and always use the default clock:

In your tests however, you might need to set the current time to test your application in known conditions. To do this, you can either explicitly pass a Clock instance to now() methods:

Or you can change the default clock for all date-time classes. All methods such as now(), unless provided with an explicit Clock, will use the default clock you provide:

There are also useful shortcut methods to use clocks in your tests, inspired by timecop:

• freeze() freezes time to a specific point in time
• travelTo() travels to an Instant in time, but allows time to continue moving forward from there
• travelBy() travels in time by a Duration, which may be forward (positive) or backward (negative)
• scale() makes time move at a given pace

Freeze the time to a specific point

Travel to a specific point in time

Make time move at a given pace

As you can see, you can even combine travelTo() and scale() methods.

Be very careful to reset() the DefaultClock after each of your tests! If you're using PHPUnit, a good place to do this is in the tearDown() method.

Exceptions

The following exceptions can be thrown:

• Brick\DateTime\DateTimeException when an illegal operation is performed
• Brick\DateTime\Parser\DateTimeParseException when parse()ing an invalid string representation

Doctrine mappings

You can use brick/date-time types in your Doctrine entities using the brick/date-time-doctrine package.

Contributing

Before submitting a pull request, you can check the code using the following tools. Your CI build will fail if any of the following tools reports any issue.

First of all, install dependencies:

Unit tests

Run PHPUnit tests:

Static analysis

Run Psalm static analysis:

Coding Style

Install Easy Coding Standard in its own folder:

Run coding style analysis checks:

Or fix issues found directly:

Rector automated refactoring

Install Rector in its own folder:

Run automated refactoring: