v3.4.3 (#1826)

## [v3.4.3] - 2024-08-08
### New Features
- Boolean/Toggle Filter by @lrljoe in #1830

### Bug Fixes
- View component column fixes by @lrljoe in #1825

### Docs
- Update setDelaySelectAllEnabled Docs by @lrljoe in #1829
- ViewComponentColumn - New method docs by @lrljoe in #1828

Author: lrljoe

.gitattributes

@@ -37,3 +37,4 @@
 /resources/js/partials/filter-date-range.js             export-ignore
 /resources/js/partials/filter-number-range.js           export-ignore
 /resources/js/partials/reorder.js                       export-ignore
+/minifyJs                                               export-ignore

.gitignore

@@ -20,4 +20,4 @@ phpunit.xml.dist.dev
 phpunit.xml.bak
 phpstan.txt
 coverage.xml
-./tmp/**
+./tmp/**

CHANGELOG.md

@@ -2,6 +2,17 @@
 
 All notable changes to `laravel-livewire-tables` will be documented in this file
 
+## [v3.4.3] - 2024-08-08
+### New Features
+- Boolean/Toggle Filter by @lrljoe in https://github.com/rappasoft/laravel-livewire-tables/pull/1830
+
+### Bug Fixes
+- View component column fixes by @lrljoe in https://github.com/rappasoft/laravel-livewire-tables/pull/1825
+
+### Docs
+- Update setDelaySelectAllEnabled Docs by @lrljoe in https://github.com/rappasoft/laravel-livewire-tables/pull/1829
+- ViewComponentColumn - New method docs by @lrljoe in https://github.com/rappasoft/laravel-livewire-tables/pull/1828
+
 ## [v3.4.2] - 2024-08-04
 ### New Features
 - Additional Events & Customisable Behaviour by @lrljoe in https://github.com/rappasoft/laravel-livewire-tables/pull/1820

docs/bulk-actions/available-methods.md

@@ -305,11 +305,29 @@ public function configure(): void
 
 This prevents the default behaviour from firing, which improves performance when working with very large sets of data.  With this feature enabled, the backend update will not fire, however an indication that all result rows have been selected will be passed to the backend, and the frontend will behave as if all rows are selected.
 
+
 When running your Bulk Action, having used "Select All", you may then access the array of "all rows" based on your most recent search/filter results:
-```
+```php
 $rows = $this->getSelectedRows();
 ```
 
+Once your bulk action completes, ensure that you call:
+```php
+$this->clearSelected();
+```
+
+### IMPORTANT NOTES
+#### Actions After Frontend Select All
+If you apply a filter/search/sort, then the delay select will be abandoned, and the array will be populated.  Ensure that you do not do this!
+
+#### Use of setSelectAll
+Do NOT call either of these methods, as they will prevent the correct method from working.  These two methods SELECT ALL regardless of what the frontend is doing.
+```php
+$this->setSelectAllStatus(true);
+$this->setSelectAllEnabled();
+```
+
+
 ## setDelaySelectAllDisabled
 
 This is the default behaviour, see setDelaySelectEnabled for details on what enabling this does.

docs/column-types/sum_column.md

@@ -5,7 +5,7 @@ weight: 13
 
 Sum columns provide an easy way to display the "Sum" of a field on a relation.
 
-```
+```php
     SumColumn::make('Total Age of Related Users')
         ->setDataSource('users','age')
         ->sortable(),

docs/column-types/view_component_column.md

@@ -15,6 +15,18 @@ ViewComponentColumn::make('E-mail', 'email')
     ]),
 ```
 
+### customComponent
+
+Should you wish to render the Custom Component in it's entirety, then you may use the customComponent method.  Otherwise it will pass in the values directly to the blade, rather than executing your View Component.
+
+```php
+ViewComponentColumn::make('Weight', 'grams')
+    ->customComponent(\App\View\Components\TestWeight::class)
+    ->attributes(fn ($value, $row, Column $column) => [
+        'weight' => new Weight($value),
+    ]),
+```
+
 Please also see the following for other available methods:
 <ul>
     <li>

docs/columns/reusable-columns.md

@@ -10,15 +10,15 @@ To mitigate the pain of maintaining this, two new methods have been introduced.
 These methods both function in exactly the same way as your standard columns(), and expect an array of columns.
 
 Any columns defined in prependColumns() will be the first columns in your list of columns.
-```
+```php
 public function prependColumns(): array
 {
     return [];
 }
 ```
 
 Any columns defined in appendColumns() will be the last columns in your list of columns.
-```
+```php
 public function appendColumns(): array
 {
     return [];
@@ -28,7 +28,7 @@ public function appendColumns(): array
 You can call these in your trait, and they will be automatically appended/prepended to tables.
 
 For example, to append a Column for Updated At 
-```
+```php
 public function appendColumns(): array
 {
     return [

docs/filter-types/filters-boolean.md

@@ -0,0 +1,39 @@
+---
+title: Boolean Filters (beta)
+weight: 2
+---
+
+## Beta
+This is currently in beta, and will only work with Tailwind.
+
+## Details
+
+The BooleanFilter is designed so that you can toggle a more complex query/filter, as opposed to being a yes/no type of filter (which is what the SelectFilter is perfect for)
+
+For example, your filter may look like this, toggling the filter from true to false would apply/not apply a more complex query to the query.
+
+```php
+    BooleanFilter::make('Limit to Older Enabled Users')
+    ->filter(function (Builder $builder, bool $enabled) {
+        if ($enabled)
+        {
+            $builder->where('status',true)->where('age', '>', 60);
+        }
+    })
+```
+
+Many of the standard methods are available, for example
+```php
+    BooleanFilter::make('Limit to Older Enabled Users')
+    ->filter(function (Builder $builder, bool $enabled) {
+        if ($enabled)
+        {
+            $builder->where('status',true)->where('age', '>', 60);
+        }
+    })
+    ->setFilterPillValues([
+        true => 'Active',
+        false => 'Inactive',
+    ])
+    ->setFilterDefaultValue(true)
+```

docs/filter-types/filters-date.md

@@ -1,6 +1,6 @@
 ---
 title: Date Filters
-weight: 2
+weight: 3
 ---
 
 Date filters are HTML date elements.

docs/filter-types/filters-daterange.md

@@ -1,6 +1,6 @@
 ---
 title: DateRange Filters
-weight: 3
+weight: 4
 ---
 
 DateRange filters are Flatpickr based components, and simply filtering by a date range.  If you would like to more smoothly filter your query by a start and end date, you can use the DateRangeFilter:
@@ -70,17 +70,17 @@ A full list of options is below, please see the Flatpickr documentation for refe
 
 You may use this to set a default value for the filter that will be applied on first load (but may be cleared by the user).  This should be an array:
 
-```
+```php
     DateRangeFilter::make('EMail Verified Range')
         ->setFilterDefaultValue(['minDate' => '2024-05-05', 'maxDate' => '2024-06-06'])
 ```
 or
-```
+```php
     DateRangeFilter::make('EMail Verified Range')
         ->setFilterDefaultValue(['min' => '2024-05-05', 'max' => '2024-06-06'])
 ```
 or
-```
+```php
     DateRangeFilter::make('EMail Verified Range')
         ->setFilterDefaultValue(['2024-05-05', '2024-06-06'])
 ```
@@ -117,26 +117,26 @@ public function filters(): array
 By default, this filter will inject the Flatpickr JS Library and CSS. However, you can customise this behaviour using the configuration file.
 
 ### Option 1 - The default behaviour:
-```
+```php
     'inject_third_party_assets_enabled' => true,
 ```
 
 ### Option 2 - Bundled
 If you choose to bundle the Tables JS/CSS (recommended) by adding the following to your build process:
 
-```
+```js
 'vendor/rappasoft/laravel-livewire-tables/resources/js/laravel-livewire-tables-thirdparty.min.js';
 ```
 
 or in your app.js
 
-```
+```js
 import '../../vendor/rappasoft/livewire-tables/resources/js/laravel-livewire-tables-thirdparty.min.js';
 ```
 
 Then you should disable injection to avoid conflicts:
 
-```
+```php
     'inject_third_party_assets_enabled' => false,
 ```
 
@@ -146,12 +146,12 @@ You must ensure that Flatpickr is present PRIOR to the tables loading.  For exam
 It is typically recommended not to utilise the CDN approach, as changes to core code may impact behaviour, and you may need to implement changes to your CSP if present.
 
 If using the CDN approach, ensure the following config matches:
-```
+```js
     'inject_third_party_assets_enabled' => false,
 ```
 
 Then include the following in your layout:
-```
+```html
 // Flatpickr Core Script
 <script src="https://npmcdn.com/flatpickr" async></script>
 
@@ -161,7 +161,7 @@ Then include the following in your layout:
 
 ### Option 4 - Locally Installed
 If you have a locally installed version of Flatpickr already, you can set injection to false, and your local version will be used instead.
-```
+```js
     'inject_third_party_assets_enabled' => false,
 ```
 
@@ -170,7 +170,7 @@ The default installation includes only the English (en) locale.
 
 ### Bundling
 Should you wish to localise, you must include the Flatpickr locale files in your build pipeline.  This applies to only the specific locales that you require in your app.js (requires adding the flatpickr library to your package.json by executing "npm i flatpickr --save")
-```
+```js
 import { Arabic } from "../imports/flatpickr/l10n/ar.js";
 import { Catalan } from "../imports/flatpickr/l10n/cat.js";
 import { Danish } from "../imports/flatpickr/l10n/da.js";
@@ -192,6 +192,6 @@ import { Ukrainian } from "../imports/flatpickr/l10n/uk.js"
 You can also add locales using the Flatpickr CDN, ensuring that these are loaded before the page renders.
 
 For example to add German (de), ensure that the following is in the "head" section of your layout, ideally before your app.js
-```
+```html
 <script src="https://npmcdn.com/flatpickr/dist/l10n/de.js" async></script>
 ```