Laravel date range

Easy handling of Laravel models that have a start / end date, or a set of date ranges.

This package is built for Laravel 8-9.

Setup

Install

composer require "greenimp/laravel-date-range:^2.0.0"

Set up the DB

If you want to use multiple date ranges on a single model, then you need to create the DB tables, unless you are using a custom model.

First, publish the migrations:

php artisan vendor:publish --provider="GreenImp\DateRange\DateRangeServiceProvider" --tag="migrations"

The run them:

Note If your config is cached, the migration will fail. You will need to clear the config cache before running the migration:

php artisan config:clear

php artisan migrate

Configuring the package

Publishing the config file is optional:

php artisan vendor:publish --provider="GreenImp\DateRange\DateRangeServiceProvider" --tag="config"

Usage

Single date ranges

If your model only requires a single start / end date (e.g. a one off event), the model must implement the HasDateRange interface, and the InteractsWithDateRange trait.

The trait contains an abstract method getDateRangeOptions, which you must implement yourself.

Your models' migrations should have datetime fields to save the start / end dates to.

Here's an example of how to implement the trait:

<?php
namespace App\Models;

use GreenImp\DateRange\Contracts\HasDateRange;
use GreenImp\DateRange\DateRangeOptions;
use GreenImp\DateRange\InteractsWithDateRange;
use Illuminate\Database\Eloquent\Model;

class SingleDateModel extends Model implements HasDateRange
{
    use InteractsWithDateRange;
    
    /**
     * Get the options for the date range.
     *
     * @return DateRangeOptions
     */
    public function getDateRangeOptions(): DateRangeOptions
    {
        return DateRangeOptions::create()
            // these are optional - if not called, the default values from the config will be used
            ->startAtField('from')
            ->endAtField('to');
    }
}

An example migration for the model:

<?php

use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;

return new class extends Migration {
    public function up()
    {
        Schema::create('your_eloquent_models', function (Blueprint $table) {
            $table->id();
            $table->datetime('from'); // Field name same as the `startAtField` in your `getDateRangeOptions`
            $table->datetime('to'); // Field name same as the `endAtField` in your `getDateRangeOptions`
            $table->timestamps();
        });
    }
}

Multiple date ranges

If your model has multiple date ranges (e.g. A repeating event such as a national holiday), the model must implement the HasDateRanges interface, and the InteractsWithDateRanges trait.

The trait adds a new dates relationship, which links to the list of date ranges.

<?php
namespace App\Models;

use GreenImp\DateRange\Contracts\HasDateRanges;
use GreenImp\DateRange\InteractsWithDateRanges;
use Illuminate\Database\Eloquent\Model;

class MultipleDateModel extends Model implements HasDateRanges
{
    use InteractsWithDateRanges;
}

Note: Unless you're using a custom model for the date ranges, then you'll need to run the migration.

Customisation

Custom Date Range model

By default, the dates relationship on the InteractsWithDateRanges trait, for multiple date ranges, will use the DateRange model that comes with this package.

If you want to use your own custom class, you can use any model that implements the HasDateRange interface, and the InteractsWithDateRange trait.

To set up your custom model, follow the instructions for creating a single date range model.

You also need to update the config file, to use your custom class:

<?php

return [
    'models' => [
        // Set the value to your custom class.
        'date_range' => \GreenImp\DateRange\Models\DateRange::class,
    ],
    ...
];

Database migration options

Table name

The migration file that comes with this package will create a table to store the DateRange models in, called date_ranges.

You can change the name of the table in the config file:

<?php

return [
    ...
    'table_names' => [
        // Set the value to your custom table name.
        'date_ranges' => 'date_ranges',
    ],
    ...
];

Table columns

You can also rename the table columns that will be used in the migration.

Note: This will also affect the default field names for the start / end dates of the DateRangeOptions class, used in the getDateRangeOptions method.