Nova-style relationship manager

[emcarson]

I was looking to implement a relationship manager similar to Nova, where you just reference the relationship in question and it automatically generates the table, reusing the same columns, query, etc.

I also didn't want to have filters, bulkActions, headerActions, etc. Just a simple table, with an Edit button that takes you to the Edit page (no modals please).

Here's what I did:

<?php

namespace App\Filament\Resources\UserResource\RelationManagers;

use App\Filament\Resources\OrderResource;
use App\Models\Order;
use Filament\Resources\RelationManagers\RelationManager;
use Filament\Resources\Table;
use Filament\Tables\Actions\Action;
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\Relations\Relation;
use Illuminate\Support\Facades\Auth;

class OrdersRelationManager extends RelationManager
{
    protected static string $relationship = 'orders';

    public static function getPluralModelLabel(): string
    {
        return 'Pedidos';
    }

    /**
     * @throws \Exception
     */
    public static function table(Table $table): Table
    {
        return (new OrderResource())->table($table)
            ->filters([])
            ->actions([
                Action::make('Editar')
                    ->icon('heroicon-s-pencil')
                    ->url(function (Order $record) {
                        return route('filament.resources.orders.edit', $record);
                    })
                    ->visible(fn (Order $record): bool => Auth::guard('admin')->user()->can('update', $record)),
            ])
            ->bulkActions([])
            ->headerActions([]);
    }

    protected function getTableQuery(): Builder | Relation
    {
        return OrderResource::getEloquentQuery()
            ->where('user_id', $this->ownerRecord->id);
    }
}

What I did was:

1. Reused the table from the resource but disabled filters, bulkActions, headerActions.
2. Replaced the default actions with a custom Edit action that is visible only if the policy allows it.
3. Reused the query from the Order resource, appending a condition to filter the records by the current resource.

[danharrin]

Here are some improvements:

<?php

namespace App\Filament\Resources\UserResource\RelationManagers;

use App\Filament\Resources\OrderResource;
use App\Models\Order;
use Filament\Resources\RelationManagers\RelationManager;
use Filament\Resources\Table;
use Filament\Tables\Actions\EditAction;
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\Relations\Relation;
use Illuminate\Support\Facades\Auth;

class OrdersRelationManager extends RelationManager
{
    protected static string $relationship = 'orders';

    public static function getPluralModelLabel(): string
    {
        return 'Pedidos';
    }

    public static function table(Table $table): Table
    {
        return OrderResource::table($table)
            ->filters([])
            ->actions([
                EditAction::make()
                    ->url(fn (Order $record): string => OrderResource::getUrl('edit', ['record' => $record])),
            ])
            ->bulkActions([])
            ->headerActions([]);
    }

    protected function getTableQuery(): Builder | Relation
    {
        return OrderResource::getEloquentQuery()
            ->where('user_id', $this->ownerRecord->id);
    }
}

[emcarson]

That's so much cleaner, thank you!