arm092 / livewire-datatables
Advanced datatables using Laravel, Livewire, Tailwind CSS and Alpine JS
Installs: 15 664
Dependents: 0
Suggesters: 0
Security: 0
Stars: 26
Watchers: 1
Forks: 258
Open Issues: 0
Requires
- php: ^8.1
- illuminate/support: ^9.0|^10.0|^11.0
- livewire/livewire: ^3.4
- maatwebsite/excel: ^3.1.57
- psr/simple-cache: ^3.0.0
- reedware/laravel-relation-joins: ^6.0
Requires (Dev)
- laravel/legacy-factories: ^1.0.4
- orchestra/testbench: ^7.0|^8.0|^9.0
- phpunit/phpunit: ^10.5
README
Features
- Use a model or query builder to supply data
- Mutate and format columns using preset or custom callbacks
- Sort data using column or computed column
- Filter using booleans, times, dates, selects or free text
- Create complex combined filters using the complex query builder
- Show / hide columns
- Column groups
- Mass Action (Bulk) Support
Live Demo App
Demo App Repo
Requirements
Installation
You can install the package via composer:
composer require arm092/livewire-datatables
Optional
You don't need to, but if you like you can publish the config file and blade template assets:
php artisan vendor:publish --provider="Arm092\LivewireDatatables\LivewireDatatablesServiceProvider"
This will enable you to modify the blade views and apply your own styling, the datatables views will be published to resources/livewire/datatables. The config file contains the default time and date formats used throughout
- This can be useful if you're using Purge CSS on your project, to make sure all the livewire-datatables classes get included
Several of the built-in dynamic components use Alpine JS, so to remove flickers on page load, make sure you have
[x-cloak] { display: none; }
somewhere in your CSS
Basic Usage
- Use the
livewire-datatable
component in your blade view, and pass in a model:
... <livewire:datatable model="App\Models\User" name="all-users" /> ...
Template Syntax
- There are many ways to modify the table by passing additional properties into the component:
<livewire:datatable model="App\Models\User" name="users" include="id, name, dob, created_at" dates="dob" />
Attention: Please note that having multiple datatables on the same page or more than one datatable of the same
type on different pages needs to have a unique name
attribute assigned to each one so they do not conflict with each
other as in the example above.
Props
Component Syntax
Create a livewire component that extends Arm092\LivewireDatatables\LivewireDatatable
php artisan make:livewire-datatable foo
--> 'app/Livewire/Datatables/Foo.php'
php artisan make:livewire-datatable foo.bar
--> 'app/Livewire/Datatables/Foo/Bar.php'
Provide a datasource by declaring public property $model
OR public method builder()
that returns an instance of Illuminate\Database\Eloquent\Builder
php artisan make:livewire-datatable users-table --model=user
--> 'app/Livewire/Datatables/UsersTable.php' withpublic $model = User::class
Declare a public method columns
that returns an array containing one or more Arm092\LivewireDatatables\Column
Columns
Columns can be built using any of the static methods below, and then their attributes assigned using fluent method chains.
There are additional specific types of Column; NumberColumn
, DateColumn
, TimeColumn
, using the correct one for your datatype will enable type-specific formatting and filtering:
use Arm092\LivewireDatatables\Column; use Illuminate\Database\Eloquent\Model; use Illuminate\Database\Eloquent\Builder; use Arm092\LivewireDatatables\DateColumn; use Arm092\LivewireDatatables\LabelColumn; use Arm092\LivewireDatatables\NumberColumn; use Arm092\LivewireDatatables\BooleanColumn; use Arm092\LivewireDatatables\Livewire\LivewireDatatable; class ComplexDemoTable extends LivewireDatatable { public function builder(): Builder { return User::query(); } public function getColumns(): array|Model { return [ NumberColumn::name('id') ->label('ID') ->linkTo('job', 6), BooleanColumn::name('email_verified_at') ->label('Email Verified') ->format() ->filterable(), Column::name('name') ->defaultSort('asc') ->group('group1') ->searchable() ->hideable() ->filterable(), Column::name('planet.name') ->label('Planet') ->group('group1') ->searchable() ->hideable() ->filterable($this->planets), // Column that counts every line from 1 upwards, independent of content Column::index($this); DateColumn::name('dob') ->label('DOB') ->group('group2') ->filterable() ->hide(), (new LabelColumn()) ->label('My custom heading') ->content('This fixed string appears in every row'), NumberColumn::name('dollars_spent') ->format(2, '.', ',') // 2 decimal places, comma for thousands, dot for decimal ->enableSummary(), ]; } }
Column Methods
Listener
The component will listen for the refreshLivewireDatatable
event, which allows you to refresh the table from external components.
Eloquent Column Names
Columns from Eloquent relations can be included using the normal eloquent dot notation, eg. planet.name
, Livewire Datatables will automatically add the necessary table joins to include the column. If the relationship is of a 'many' type (HasMany
, BelongsToMany
, HasManyThrough
) then Livewire Datatables will create an aggregated subquery (which is much more efficient than a join and group. Thanks @reinink). By default, the aggregate type will be count
for a numeric column and group_concat
for a string column, but this can be over-ridden using a colon delimeter;
NumberColumn::name('students.age:sum')->label('Student Sum'), NumberColumn::name('students.age:avg')->label('Student Avg'), NumberColumn::name('students.age:min')->label('Student Min'), NumberColumn::name('students.age:max')->label('Student Max'),
Column Groups
When you have a very big table with a lot of columns, it is possible to create 'column groups' that allows the user to toggle the visibility of a whole group at once. Use ->group('NAME')
at any column to achieve this.
You can human-readable labels and translations of your groups via the groupLabels
property of your table:
use Arm092\LivewireDatatables\Column; use Illuminate\Database\Eloquent\Model; use Arm092\LivewireDatatables\Livewire\LivewireDatatable; class GroupDemoTable extends LivewireDatatable { public array $groupLabels = [ 'group1' => 'app.translation_for_group_1', 'group2' => 'app.translation_for_group_2', ]; public function getColumns(): array|Model { return [ Column::name('planets.name') ->group('group1') ->label('Planet'), Column::name('planets.name') ->group('group2') ->label('Planet'),
Summary row
If you need to summarize all cells of a specific column, you can use enableSummary()
:
public function getColumns(): array|Model { return [ Column::name('dollars_spent') ->label('Expenses in Dollar') ->enableSummary(), Column::name('euro_spent') ->label('Expenses in Euro') ->enableSummary(),
Mass (Bulk) Action
If you want to be able to act upon several records at once, you can use the buildActions()
method in your Table:
public function buildActions(): array { return [ Action::value('edit')->label('Edit Selected')->group('Default Options')->callback(function ($mode, $items) { // $items contains an array with the primary keys of the selected items }), Action::value('update')->label('Update Selected')->group('Default Options')->callback(function ($mode, $items) { // $items contains an array with the primary keys of the selected items }), Action::groupBy('Export Options', function () { return [ Action::value('csv')->label('Export CSV')->export('SalesOrders.csv'), Action::value('html')->label('Export HTML')->export('SalesOrders.html'), Action::value('xlsx')->label('Export XLSX')->export('SalesOrders.xlsx')->styles($this->exportStyles)->widths($this->exportWidths) ]; }), ]; }
Mass Action Style
If you only have small style adjustments to the Bulk Action Dropdown you can adjust some settings here:
public function getExportStylesProperty(): array { return [ '1' => ['font' => ['bold' => true]], 'B2' => ['font' => ['italic' => true]], 'C' => ['font' => ['size' => 16]], ]; } public function getExportWidthsProperty(): array { return [ 'A' => 55, 'B' => 45, ]; }
Pin Records
If you want to give your users the ability to pin specific records to be able to, for example, compare them with each other, you can use the CanPinRecords trait. Ensure to have at least one Checkbox Column so the user can select records:
use Arm092\LivewireDatatables\Column; use Illuminate\Database\Eloquent\Model; use Arm092\LivewireDatatables\Traits\CanPinRecords; use Arm092\LivewireDatatables\Livewire\LivewireDatatable; class RecordTable extends LivewireDatatable { use CanPinRecords; public string|null|Model $model = Record::class; public function getColumns(): array|Model { return [ Column::checkbox(), // ...
Custom column names
It is still possible to take full control over your table, you can define a builder
method using whatever query you like, using your own joins, groups whatever, and then name your columns using your normal SQL syntax:
public function builder(): Builder { return User::query() ->leftJoin('planets', 'planets.id', 'users.planet_id') ->leftJoin('moons', 'moons.id', 'planets.moon_id') ->groupBy('users.id'); } public function getColumns(): array|Model { return [ NumberColumn::name('id') ->filterable(), Column::name('planets.name') ->label('Planet'), Column::raw('GROUP_CONCAT(planets.name SEPARATOR " | ") AS `Moon`') ->setCallback(static fn($value) => strtolower($value)) ... }
Callbacks
Callbacks give you the freedom to perform any mutations you like on the data before displaying in the table.
- The callbacks are performed on the paginated results of the database query, so shouldn't use a ton of memory
- Callbacks will receive the chosen columns as their arguments.
- Callbacks can be defined inline as below, or as public methods on the Datatable class, referenced by passing the name as a string as the second argument to the callback method.
- If you want to format the result differently for export, use
->exportCallback(Closure $callback)
.
use Arm092\LivewireDatatables\Column; use Illuminate\Database\Eloquent\Model; use Arm092\LivewireDatatables\Livewire\LivewireDatatable; class CallbackDemoTable extends LivewireDatatable { public string|null|Model $model = User::class public function getColumns(): array|Model { return [ Column::name('users.id'), Column::name('users.dob')->format(), Column::callback(['dob', 'signup_date'], function ($dob, $signupDate) { $age = $signupDate->diffInYears($dob); return $age > 18 ? '<span class="text-red-500">' . $age . '</span>' : $age; })->exportCallback(function ($dob, $signupDate), { return $age = $signupDate->diffInYears($dob); }), ... } }
Default Filters
If you want to have a default filter applied to your table, you can use the defaultFilters
property. The defaultFilter
should be an Array of column names and the default filter value to use for. When a persisted filter ($this->persistFilters
is true and session values are available) is available, it will override the default filters.
In the example below, the table will by default be filtered by rows where the deleted_at column is false. If the user has a persisted filter for the deleted_at column, the default filter will be ignored.
use Arm092\LivewireDatatables\Column; use Illuminate\Database\Eloquent\Model; use Illuminate\Database\Eloquent\Builder; use Arm092\LivewireDatatables\BooleanColumn; use Arm092\LivewireDatatables\Livewire\LivewireDatatable; class CallbackDemoTable extends LivewireDatatable { public array $defaultFilters = [ 'deleted_at' => '0', ]; public function builder(): Builder { return User::query()->withTrashed(); } public function getColumns(): array|Model { return [ Column::name('id'), BooleanColumn::name('deleted_at')->filterable(), ]; } }
Views
You can specify that a column's output is piped directly into a separate blade view template.
- Template is specified using ususal laravel view helper syntax
- Views will receive the column's value as
$value
, and the whole query row as$row
use Arm092\LivewireDatatables\Column; use Illuminate\Database\Eloquent\Model; use Arm092\LivewireDatatables\Livewire\LivewireDatatable; class CallbackDemoTable extends LivewireDatatable { public string|null|Model $model = User::class public function getColumns(): array|Model { return [ Column::name('users.id'), Column::name('users.dob')->view('tables.dateview'), Column::name('users.signup_date')->format(), ]; }
'tables/dateview.blade.php' <span class="mx-4 my-2 bg-pink-500"> <x-date-thing :value="$value" /> </span>
Editable Columns
You can mark a column as editable using editable
This uses the view()
method above to pass the data into an Alpine/Livewire compnent that can directly update the underlying database data. Requires the column to have column
defined using standard Laravel naming. This is included as an example. Much more comprehensive custom editable columns with validation etc can be built using the callback or view methods above.
use Arm092\LivewireDatatables\Column; use Illuminate\Database\Eloquent\Model; use Arm092\LivewireDatatables\Livewire\LivewireDatatable; class EditableTable extends LivewireDatatable { public string|null|Model $model = User::class; public function getColumns(): array|Model { return [ Column::name('id') ->label('ID') ->linkTo('job', 6), Column::name('email') ->editable(), ... ]; } }
Complex Query Builder
Just add $complex = true
to your Datatable Class and all filterable columns will be available in the complex query builder.
Features
- Combine rules and groups of rules using AND/OR logic
- Drag and drop rules around the interface
Persisting Queries (Requires AlpineJS v3 with $persist plugin)
- Add
$persistComplexQuery = true
to your class and queries will be stored in browser localstorage. - By default, the localstorage key will be the class name. You can provide your own by setting the public property
$persistKey
or overridinggetPersistKeyProperty()
on the Datatable Class - eg: for user-specific persistence:
public function getPersistKeyProperty() { return Auth::id() . '-' . parent::getPersistKeyProperty(); }
Saving Queries
If you want to permanently save queries you must provide 3 methods for adding, deleting and retrieving your saved queries using whatever logic you like:
public function saveQuery(string $name, array $rules)
public function deleteQuery(int $id)
public function getSavedQueries()
- In your save and delete methods, be sure to dispatch an
updateSavedQueries
livewire event and pass a fresh array of results (see example below)
Example:
This example shows saving queries using a conventional Laravel ComplexQuery model, that belongsTo a User
/* Migration */ use Illuminate\Database\Migrations\Migration; use Illuminate\Database\Schema\Blueprint; use Illuminate\Support\Facades\Schema; return new class extends Migration { public function up() { Schema::create('complex_queries', static function (Blueprint $table) { $table->id(); $table->unsignedInteger('user_id'); $table->string('table'); $table->json('rules'); $table->string('name'); $table->timestamps(); }); } public function down(): void { Schema::dropIfExists('complex_queries'); } }; /* Model */ class ComplexQuery extends Model { protected $casts = ['rules' => 'array']; public function user() { return $this->belongsTo(User::class); } } /* Datatable Class */ class TableWithSaving extends LivewireDatatable { ... public function saveQuery($name, $rules): void { Auth::user()->complex_queries()->create([ 'table' => $this->name, 'name' => $name, 'rules' => $rules ]); $this->dispatch('updateSavedQueries', $this->getSavedQueries()); } public function deleteQuery($id): void { ComplexQuery::destroy($id); $this->dispatch('updateSavedQueries', $this->getSavedQueries()); } public function getSavedQueries(): void { return Auth::user()->complex_queries()->where('table', $this->name)->get(); } ... }
Styling
I know it's not cool to provide a package with tons of opionated markup and styling. Most other packages seem to have gone down the route of passing optional classes around as arguments or config variables. My take is that because this is just blade with tailwind, you can publish the templates and do whatever you like to them - it should be obvious where the Livewire and Alpine moving parts are.
There are methods for applying styles to rows and cells. rowClasses
receives the $row
and the laravel loop variable as parameters. cellClasses
receives the $row
and $column
For example:
public function rowClasses($row, $loop): string { return 'divide-x divide-gray-100 text-sm text-gray-900 ' . ($this->rowIsSelected($row) ? 'bg-yellow-100' : ($row->{'car.model'} === 'Ferrari' ? 'bg-red-500' : ($loop->even ? 'bg-gray-100' : 'bg-gray-50'))); } public function cellClasses($row, $column): string { return 'text-sm ' . ($this->rowIsSelected($row) ? ' text-gray-900' : ($row->{'car.model'} === 'Ferrari' ? ' text-white' : ' text-gray-900')); }
You can change the default CSS classes applied by the rowClasses
and the cellClasses
methods by changing default_classes
in the livewire-datatables.php
config file.
You could also override the render method in your table's class to provide different templates for different tables.