Fix: configure using emptyStateDescription

[borjajimnz]

Description

As described in #14990, I'm not sure if this is the expected behavior. At least for me, it seems to be. @danharrin

This is the current priority order:

1. Resource
2. Configure using
3. If nothing is set, but the create action is there, it will display the "Create a %% to get started." text.

Visual changes

https://youtu.be/1gzuXzNHWDs

Functional changes

• Code style has been fixed by running the composer cs command.
• Changes have been tested to not break existing functionality.
• Documentation is up-to-date.

[CodeWithDennis]

Came here to look for exactly this issue.

 Table::configureUsing(function (Table $table): void {
     $table->emptyStateDescription(__('It looks like we couldn\'t find any records'));
 });

Is this gonna be merged in the current version or waiting for V4?

[danharrin]

I'm not sure yet, I don't think the implementation is right here but I've not had time to work out a proper alternative

[CodeWithDennis]

This idea is "somewhat" related but doesn't fix the issue itself.

Wouldn't it make sense to replace the following with a default description as well, since that's what getEmptyStateHeading also does?

public function getEmptyStateDescription(): string | Htmlable | null
{
    return $this->evaluate($this->emptyStateDescription);
}

Replace with:

public function getEmptyStateDescription(): string | Htmlable | null
{
    return $this->evaluate($this->emptyStateDescription) ?? __('filament-tables::table.empty.description', [
        'model' => $this->getModelLabel(),
    ]);
}

[danharrin]

Would break being able to remove the description with emptyStateDescription(null)

[danharrin]

In v4 I have changed the feature so that any parent defined configure() statements are called before setUp(), and any child ones are called after setUp() - c91a51d

This will hopefully prevent similar issues in the future