Add setFilterSlidedownWrapperAttributes and setFilterSlidedownRowAttributes

[lrljoe]

Adds two new methods to the Component:

• setFilterSlidedownWrapperAttributes
• setFilterSlidedownRowAttributes

Also:

• Separates per-filter and per-table methods into separate doc sections

setFilterSlidedownWrapperAttributes

Allows for the customisation of the appearance of the Filter Slidedown Wrapper.

You may also replace default colors by setting "default-colors" to false, or default styling by setting "default-styling" to false, and specifying replacement classes in the "class" property.

You can also replace the default transition behaviours (Tailwind) by specifying replacement attributes in the array, for example to extend the duration of the transition effect from the default duration-100 to duration-1000:

public function configure(): void
{
    $this->setFilterSlidedownWrapperAttributes([
        'x-transition:enter' => 'transition ease-out duration-1000',
        'class' => 'text-black',
        'default-colors' => true,
        'default-styling' => true, 
    ]);
}

setFilterSlidedownRowAttributes

Allows for the customisation of the appearance of the Filter Slidedown Row. Note that this uses a callback, which receives the "rowIndex" of the Slidedown Row

You may replace default colors by setting "default-colors" to false, or default styling by setting "default-styling" to false, and specifying replacement classes in the "class" property.

public function configure(): void
{
    $this->setFilterSlidedownRowAttributes(fn($rowIndex) => $rowIndex % 2 === 0 ? 
        [
            'class' => 'bg-red-500',
            'default-colors' => true,
            'default-styling' => true, 
        ] :  [
            'class' => 'bg-blue-500',
            'default-colors' => true,
            'default-styling' => true, 
        ] 
    );
}

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?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.36%. Comparing base (a931da9) to head (a1ee4e9).
Report is 1 commits behind head on development.

Additional details and impacted files

@@                Coverage Diff                @@
##             development    #2120      +/-   ##
=================================================
+ Coverage          90.33%   90.36%   +0.02%     
- Complexity          1940     1945       +5     
=================================================
  Files                189      189              
  Lines               4376     4388      +12     
=================================================
+ Hits                3953     3965      +12     
  Misses               423      423              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.