Download the PHP package brickx/calendax without Composer

Livewire calendar for Laravel

NOTE: This package is intended for my own use only, so a few things are very specific to my projects (e.g. importing .tsx & .scss uncompiled files directly).

If anyone is interested in making it easier to set up and more maintainable for a wider audience, please submit a PR or open a discussion!

Also, feel free to consider using the package on which this one is based as stated below.

Calendax allows you to build a Livewire calendar, filled with events of any kind. Events can be created from any model or dataset.

It is heavily inspired by Andrés Santibáñez's Livewire Calendar.

Preview

Table of contents

• Installation
• Requirements
• Usage
  • Initialization
  • Loading events (using arrays)
  • Loading events (using Eloquent query)
  • Rendering the calendar
  • Choosing the starting month
  • Enabling drag & drop
  • Handling navigation
• Advanced usage
  • Blade customization
  • Custom views
  • Interactivity
  • Automatic polling
• Flatpickr
  • Importing
  • Customization
• Testing

Installation

You can install the package via composer:

You can publish the config file with:

This is the contents of the published config file:

Optionally, you can publish the views using

Requirements

This package uses livewire/livewire (https://laravel-livewire.com) under the hood.

It also uses TailwindCSS (https://tailwindcss.com) for styling. Please make sure you include both of these dependencies before using this component.

Usage

Initialization

First, create a new Livewire component that extends Calendax.

You can use make:livewire to create this component. For example:

Then, in the created MyCalendar class, extend Calendax instead of extending from the base Component Livewire class:

In this class, you must override the following method in order to implement custom logic for loading events:

Also remove the render method, as it will be handled for you.

In the events() method, you should return a collection containing the events that should be displayed on the calendar.

Loading events (using arrays)

Events must be keyed arrays holding at least the following keys: id, title, description, date (which must be a Carbon\Carbon instance).

The date value will be used to determine to which day the event will be displayed.

Loading events (using Eloquent query)

You can also load values dynamically in the events() method. You can use the following component properties to filter your events:

• startsAt: starting date of the month
• endsAt: ending date of the month
• gridStartsAt: starting date of calendar grid (can be a date from the previous month).
• endingStartsAt: ending date of calendar grid (can be a date from the previous month).

Rendering the calendar

Now you can include your calendar in any view using Blade components:

This will render a calendar grid.

Choosing the starting month

By default, the component will render the current month. If you want to change the starting month, you can set the year and month props.

Enabling drag & drop

To enable drag & drop, include @calendaxScripts after your @livewireScripts directive.

Handling navigation

The component has 4 public methods used to navigate between months:

For example, these methods can be used to build a navigation system using additional views. Check out below section for example usage.

Advanced usage

Blade customization

When rendering your Blade component, several additional attributes are available to customize the behavior of your calendar:

• week-start to indicate the starting day of the week. It can be a number from 0 to 6 according to Carbon days of week (0 = sunday).

• drag-and-drop-classes can be any CSS class used to render the hover effect when dragging & dropping an event in the calendar. By default, this value is border border-4 border-blue-400.

Custom views

You can also use custom Blade views to render different parts of the calendar.

It is recommended to publish the base Blade views used by the component and extend their behavior and styling to your liking. To do this, please check out the Installation section.

Those views can be specified using the following attributes:

• calendar-view used to render the whole component. Please check out the package's calendar.blade.php view to know which attributes are available.

• dow-view used to render each column header of the calendar (typically containing days of week). This view will receive the $dayproperty, which is a Carbon instance of the associated day of the week.

• day-view used to render each day of the month. This view will receive the following attributes:

  • componentId (the id of the Livewire component)
  • day (the day of the month as a Carbon instance)
  • dayInMonth (boolean indicating if the day is part of the current month or not)
  • isToday (boolean indicating if the day is today)
  • events (events collection that corresponds to the day)

• event-view used to render the event card. This view will receive an $event variable containing its data.

• before-calendar-view and after-calendar-view can be any Blade views that will be rendered before or after the calendar itself. These can be used to add extra features ( e.g. navigation system) to your component.

All custom views paths must be relative to the resources/views directory.

Interactivity

Several methods are available to interact with the calendar:

You can override any of them to implement your custom logic.

By default, click and drag & drop events are enabled. To disable them you can use the following attributes when rendering the component

Automatic polling

You can add automatic polling if need be by defining a $pollMillis property in the Livewire component.

You can also combine it with $pollAction in order to call a specific action in your component at the desired polling interval.

To learn more about polling, please check out https://laravel-livewire.com/docs/2.x/polling.

Flatpickr

To handle navigation between months, this package makes use of the Flatpickr library. It displays a calendar picker which is way more powerful than simple <select>.

Importing

First, add the Flatpickr library to your package.json's dependencies:

Then import this package's flatpickr.scss and flatpickr.tsx files to you main stylesheet & script.

app.scss:

app.js:

Customization

You can customize the colors of the calendar picker to match your theme. To do so, simply override the Sass variables when importing flatpickr.scss:

Testing

You can test the component using Pest by running the following commands, depending on your needs.

Standard test:

With coverage:

Parallel test:

Parallel test with coverage:

Todo

• [ ] Ideally, users should not have to mess with their sass & script files in order to import the proper dependencies. Everything should be done inside Blade (at the very least importing styles & script directly in Blade layout). See: https://github.com/Laratipsofficial/laravel-flatpickr.
• [ ] Find a way to highlight events in Flatpickr component (so that users see immediately which days have events).
• [ ] Handle Shields properly in README.md. Check out: https://shields.io/.
• [X] Create tests for Flatpickr component
• [X] Update README.md for how to properly setup Flatpickr component
• [X] Add default navigation, ideally using a dynamic calendar picker (instead of basic <select>).

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Florian PLAMONT
• Andrés Santibáñez
• All Contributors

License

The MIT License (MIT). Please see License File for more information.