Action support single table inheritance record

[theofanisv]

Description

I have a model that uses single table inheritance.
This can lead to different models being rendered by executing a query on the parent one, example:

class Admin extends User {
 // ...
}

$users = User::all();

assert($users[0] instanceof \App\Models\User);
assert($users[1] instanceof \App\Models\Admin);

Let's say I have a filament resource to display all users (mixed models) and run some actions that are common to both models. Then I have lost the ability to customize the fields of the action because the recordKey is not being sent in front-end (via the click handler) so later is not being sent back to the back-end.
That is because the condition $record::class === $table->getModel() will return false when (as per the example above) the record is Admin because the table model (parent model) is User. I changed the condition in order to accommodate the previous functionality (as much as I can understand) and support my use case.

The condition I changed was implemented in #17786, but I do not understand how it solved that related issue. The filament resource and its actions were working correctly until that update.

In case my implementation is not accepted, can you please suggest a workaround in order to continue my use case?

Visual changes

No visual changes.

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.

[danharrin]

whoops