v3.4.21

[lrljoe]

Significant change to the way that custom attributes work. Adds in some core methods for setting/getting custom attributes

There is one major change still to come which is to:

• Add additional tests for the custom attributes.

This should help to standardise behaviour for attributes.

These will come in a subsequent release!

A short period of testing will ensue prior to this release.

Bulk Actions

Replaces internal code for setting custom attributes for some attributes:

• BulkActionsButtonAttributes
• BulkActionsMenuAttributes
• BulkActionsMenuItemAttributes
• BulkActionsThAttributes
• BulkActionsThCheckboxAttributes
• BulkActionsTdAttributes
• BulkActionsTdCheckboxAttributes
  Public methods remain unchanged

Begins replacing several duplicate tests with smoother data provider based test

Columns

Generic Columns

Adds some generic column generation for the table head to allow for use of setThAttributes for these columns for:

• Bulk Action Columns
• Reorder Columns
  Docs updated for this

Column Labels

Adds a new method for customising Column Label Attributes
The Column itself provides the capability to style the Label shown in the "th" element. You can set custom attributes to pass to the Column Label on a per-Column basis:

For example:

Column::make('Name')
    ->setLabelAttributes(['class' => 'text-2xl'])

By default, this replaces the default classes on the label, if you would like to keep them, set the default/default-styling/default-colors flags to true as appropriate.

Blades

Adds the "default-colors" and "default-styling" ignore attributes, splits much of the default styling classes into these categories to make replacing defaults smoother.
i.e. replaces

->except('default') 

with

->except(['default','default-styling','default-colors']) 

In almost all cases (even when default-styling/default-colors are not presently used!

[v3.4.21] - 2024-09-25

Bug Fixes

• Remove persist from getFilterGenericData by @lrljoe in Remove persist from getFilterGenericData #1966
• In LaravelLivewireTablesEvent, change the type to Illuminate\Contracts\Auth\Authenticatable by @khwadj in [FIXES #1949] In LaravelLivewireTablesEvent, change the type of $user to Illuminate\Contracts\Auth\Authenticatable #1963
• Fix for Search Field Attribute Defaults by @lrljoe in Fix for Search Field Attribute Defaults #1962
• Fix Filter Pills Icon - Tailwind by @lrljoe in Fix Filter Pills Icon - Tailwind #1961
• Add filterComponents into queryString to ensure they're maintained by @lrljoe in Add filterComponents into queryString to ensure they're maintained #1957
• Reset Current Page on "Per Page" changing by @lrljoe in Reset Current Page on "Per Page" changing #1953

New Features

• Add setLabelAttributes method to Action, and update Docs for Filter by @lrljoe in Add setLabelAttributes method to Action, and update Docs for Filter #1952

Tweaks

• Migration to Core attribute management by @lrljoe in Migration to Core attribute management #1943
• Localisation - Avoid Conflicts With Other Packages by @lrljoe in Localisation - Avoid Conflicts With Other Packages #1955
• GitHub Workflow Tweak for Styling Fixes by @lrljoe in Update Pint Workflow #1967
• GitHub Workflow Tweak for Discord - Updates by @lrljoe in Update Discord Releases Workflow #1968

Docs

• Fix syntax for DateColumn outputFormat in docs by @lrljoe in Fix syntax for DateColumn outputFormat in docs #1960

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. Does your submission pass tests and did you add any new tests needed for your feature?
2. Did you update all templates (if applicable)?
3. Did you add the relevant documentation (if applicable)?
4. Did you test locally to make sure your feature works as intended?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?