https://filamentphp.com/docs/4.x/tables/custom-data on Resource needs $record of type Model

[karmic frost]

in filament/filament/src/Resources/Pages/ListRecord.php

on line 129:

->recordAction(function (Model $record, Table $table): ?string {

and on line 162:

if (! $table->hasCustomRecordUrl()) {
    $table->recordUrl(function (Model $record, Table $table): ?string {

still only accepts a "Model". but when using "custom data" as per documentation. the return type of a record is an array. so it should be

(Model|array $record, Table $table)

or do i need to do something else so it behaves like a "Model".?

[vocal saffron]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[zealous crypt]

I believe Filament Resources are designed to work with Eloquent Models. One approach would be to use Sushi package, or you could create your own classes to build a similar Resource class.

[karmic frost]

Okay understand. I used to use the sushi package. But that article said it could be done this way.

[zealous crypt]

what article?

[karmic frost]

https://filamentphp.com/insights/alexandersix-all-about-the-filament-v4-beta-release#static-table-data

[zealous crypt]

it says Filament table, not Resources, right?
Resources in the docs: "Resources are static classes that are used to build CRUD interfaces for your Eloquent models"

[karmic frost]

Yeah that’s true. But i thought as resource holds a public table() function it inherits this.

Anyway, when just adding this Model|array it also works in resources.

[zealous crypt]

what about protected static ?string $model = xx in Resources?

[karmic frost]

Not sure what you mean. I think I removed that in my Resource. And it’s a nullable string. Not a Model type. So I’m not sure what you mean with that?

[zealous crypt]

if it is null and the resource is working, I think you could open a PR with this suggestion.
But not sure about other resource parts that use a Model with reference

[karmic frost]

Will check that out before i do a PR 💪🏻

[karmic frost]

@zealous crypt maybe for the Actions added to the table or headerActions it needs a Model type (not sure)... but i do see that the Trait InteractsWithRecord also accepts an array as record on many functions.. getRecord() , record(), ensureCorrectRecordType(), resolveRecordKey()

also i see when adding

public static function getPages(): array
{
        return [
            'index' => Pages\ListAccounts::route('/'),
            'edit' => Pages\EditAccount::route('/{record}'),
            'create' => Pages\CreateAccount::route('/create'),
        ];
    }

then in ListRecords.php line 202
i also get this problem:

  if (! $resource::{'can' . ucfirst($action)}($record)) {
                        continue;
                    }

so better convert my resource to a simple Page. anyway thanks for clarification. i just thought creating a resource which can CRUD in sync with an API instead of a Model would this (using a Resource) be the better way.

[zealous crypt]

yes, agree with custom pages ✌️