Livewire PowerGrid is a component for generating dynamic tables with your Laravel Models.

PowerGrid comes with a variety of out-of-the-box features:

✅ Searching & Filters

✅ Column Sorting

✅ Pagination

✅ Action checkboxes

✅ Action buttons

✅ Toggle button

✅ Click to edit

✅ Click to copy

✅ Link inside a table cell

✅ Data Export to XLSX/CSV

✅ Works with Bootstrap or Tailwind CSS

✅ Translations available for 🇺🇸 🇧🇷 🇪🇸 🇩🇪 and more to come...

• Livewire PowerGrid
  • What is Livewire PowerGrid?
• Get started
  • Requirements
  • Installation
    • 1. Via composer
    • 2. Publish Config files
    • 3. Publish files [OPTIONAL]
    • 4. Configure the theme and Alpine JS
    • 5. Include PowerGrid component
    • 6. Creating a Table Component
    • 6.1 Create with Fillable
    • 6.2 Create options
    • 7. Using your Table Component
  • Configuring and Customizing
    • setUp() Method
    • dataSource() Method
      • Column Settings
      • Column Filters
      • Column Actions
    • Action Methods
    • Update Method
  • Examples
  • Demo
  • Support
  • Contributors
  • Credits

• Laravel 8x
• Livewire 2x
• Tailwind or bootstrap:
  • Install Tailwindcss
  • Install Bootstrap 5

This documentation will describe the creation of a table called ProductTable used to list products of the Product Model.

To install via composer, run:

  composer require power-components/livewire-powergrid

Publish the Livewire PowerGrid configuration file with the following command:

    php artisan vendor:publish --tag=livewire-powergrid-config

This step is OPTIONAL. Skip it if you don't need to customize Livewire PowerGrid.

Language files can be published with:

Views:

    php artisan vendor:publish --tag=livewire-powergrid-views

Language files can be published with:

    php artisan vendor:publish --tag=livewire-powergrid-lang

By default, PowerGrid uses Tailwind.

This configuration can be changed in the file config/livewire-powergrid.php.

For Bootstrap 5 use:

    //...
    'theme' => 'bootstrap'

For Tailwind use:

    //...
    'theme' => 'tailwind'

Alpine JS is not mandatory but it is required by features like "Click to edit" and "Toggable".

To activate it, open the file config/livewire-powergrid.php and modify the 'js_framework' setting replacing null with 'alpinejs'.

    //...
    'js_framework' => 'alpinejs',

The CDN for Alpine JS is configured by default, in the same file:

    //...
    'js_framework_cdn' => [
        'alpinejs' => 'https://cdn.jsdelivr.net/gh/alpinejs/alpine@v2.8.2/dist/alpine.min.js'
    ]

Include the Livewire and the PowerGrid styles and scripts:

...
    <!-- Styles -->
    @livewireStyles
    @powerGridStyles

   </head>

...
    <!-- Scripts -->
    @livewireScripts
    @powerGridScripts

</body>

You can read more about this at the official Livewire documentation

To create a Table Component run powergrid:create informing your table name and your model.

Example:

php artisan powergrid:create ProductTable --model="App\Models\Product" 

(It's advisable to use "" around your --model option)

If your Model has the fillable property specified, use --fillable option to create columns based on its value.

php artisan powergrid:create ProductTable --model="App\Models\Product" --fillable

If everything was successful, you will find your new table component inside the app/Http/Livewire folder.

The command powergrid:create accepts the following options:

The ProductTable component can be included in any view.

There are two ways to do that. Both work in the same way:

    <livewire:product-table/>

or

  @livewire('product-table')

You can configure and customize your table component to adjust it to your needs.

You can view more functionalities consulting each of the following methods:

• setUp()
• dataSource()
• Column Methods
• Action Methods

The Setup method is used to configure your component.

Example of usage:

  public function setUp()
  {
      $this->showCheckBox()
      ->showRecordCount('short')
      ->showPerPage()
      ->showSearchInput()
      ->exportedFileName('export');
  }

The dataSource() method is responsible for feeding data to your table.

It expects a model collection in the variable $model. Relationships can also be included.

Example:

 $model = Product::query()->with('group')->get();

Here $model is receiving all products with the relationship to groups.

For instance, the product "Mouse" belongs to "Computer" group, the product "A4 Paper" belongs to "Office Supplies" group.

Example of usage:

return PowerGrid::eloquent($model)
    ->addColumn('id')
    ->addColumn('name')
    ->addColumn('size')

    /** Group Relationship **/
    ->addColumn('group_id', function (Product $product) {
        return  $product->group_id;
    })
    ->addColumn('group_name', function (Product $product) {
        return  $product->group->name;
    })

    /** Active Boolean **/
    ->addColumn('is_active')
    ->addColumn('is_active_label', function (Product $product) {
        return ($product->is_active ? "active" : "inactive");
    })

    /** Price Format **/
    ->addColumn('price')
    ->addColumn('price_formatted', function(Product $product) {
        return  '$ ' . number_format($product->price, 2, ',', '.');
    })

    /** Created Date Format **/
    ->addColumn('created_at')
    ->addColumn('created_at_formatted', function(Product $product) {
      return Carbon::parse($product->created_at)->format('d/m/Y H:i');
    })
    ->make();

The data of each column can be manipulated with a closure function.

  ->addColumn('price') 
   //will output 1500.00

The example below brings the price formated.

  ->addColumn('price_formatted', function(Product $product) {
      return  '$ ' . number_format($product->price, 2, ',', '.');
    })
    //will output $ 1.500,00

The custom currency format should be converted back in the updated method as demonstrated below.

The column group_id is added for the relationship filter and the column group_name will bring the group data via the relationship.

    ->addColumn('group_id', function (Product $product) {
        return  $product->group_id;
    })
    ->addColumn('group_name', function (Product $product) {
        return  $product->group->name;
    })

These are the methods available on each column added with the Column class.

These are the filters available for each column.

These are the actions available for each column.

Example of usage:

The example below will render a column for the attribute name, with the title "Product Name". This column will be searchable by the main search field, will allow editing the values on click, and have its own input box filter on top.

    $canEdit = true; // this role has permission to edit

    Column::add()
        ->title(__('Product Name'))
        ->field('name')
        ->searchable()
        ->editOnClick($canEdit)
        ->clickToCopy()
        ->makeInputText()
        ->sortable(),

The next example will bring a column with the date formatted and with a date filter for it.

  Column::add()
      ->title('Creation date')
      ->field('created_at_formatted')  //Displays formatted data dd/mm/YYY to the user
      ->makeInputDatePicker('created_at') //Uses unformatted data
      ->searchable()

The example below renders a min-max amount filter and configures it to handle the custom currency formatting ($ 85.133,84). The method makeInputRange references the price attribute, while the column outputs the price_formatted.

  Column::add()
      ->title(__('US Price'))
      ->field('price_formatted')
      ->makeInputRange('price', '.', ','),

Boolean column example:

   $canEditStatus = true; // permission for editing
   
   Column::add()
      ->title(__('Status'))
      ->field('is_active'),
      ->toggleable($canEditStatus, 'active', 'inactive') // Toggleable. If false, instead will render "active/inactive"
      ->makeBooleanFilter('is_active', 'active', 'inactive'), // Filter with "active/inactive" labels

NOTE

Performing data updating with features like clickToEdit and Toggleable will require you to have the update() method uncommented and configured. Alpine JS must be activated.

These methods are available on the Button class.

Example of usage:

 return [
    Button::add('destroy')
        ->caption(__('Delete'))
        ->class('btn btn-danger')
        ->route('product.destroy', ['product' => 'id'])
        ->method('delete'),
  //...
];

The update method needs to be activated and configured for the edit on click and toggle to work.

All data sent by the user should go under validation and treatment. For instance, the user sends price_formatted with the value of $ 4.947,70 to update the Product price. The database has the field price and expects 44947.70. The developer must handle this data and point where to save it. Powergrid will not perform this conversion automatically. The same would happen with dates. See the two basic examples below:

public function update(array $product): bool
{

        /**
        * Reverts "price_formatted" to the database format and saves in the 'price' field.
        *  $ 4.947,70 --> 44947.70
        **/

        if ($data['field'] == 'price_formatted') {
              $data['field'] = 'price'; //Update the field price
              $data['value'] = Str::of($data['value'])
                ->replace('.', '')
                ->replace(',', '.')
                ->replaceMatches('/[^Z0-9\.]/', '');
        }

        /**
        *  Parses the date from d/m.Y (25/05/2021) 
        **/
         if ($data['field'] == 'created_at_formatted' && $data['value'] != '') {
            $data['field'] = 'created_at'; // Updates created_at
            $data['value'] =  Carbon::createFromFormat('d/m/Y', $data['value']);
         }

      try {
          $updated = Product::query()->find($product['id'])->update([
              $product['field'] => $product['value']
          ]);
      } catch (QueryException $exception) {
          $updated = false;
      }
      return $updated;
}

The update() method supports custom messages for each field.

To modify the displayed message after saving data, edit or add items on the updateMessages() method.

    public function updateMessages(string $status, string $field = '_default_message'): string
    {
        $updateMessages = [
            'success'   => [
              '_default_message' => __('Data has been updated successfully!'),
               //...
              'name' => __('Product name updated successfully!'), // Custom message for name field
              ],

            "error" => [
              '_default_message' => __('Error updating the data.'),
               //'custom_field' => __('Error updating custom field.'),
            ]

        ];

        return ($updateMessages[$status][$field] ?? $updateMessages[$status]['_default_message']);
    }

Tailwind table

Excel export

• Demo project created for a live at Beer and Code Youtube channel.

If you need any support, please check our Issues. You can ask questions or report problems there.

Created by: Luan Freitas

Contributors (in alphabetical order):

• Claudio Pereira
• @DanSysAnalyst
• Mateus Guimarães
• Tiago Braga

• Contributions
• Online Logomaker
• Admin Template used in example screenshot.