-
When creating a unique experience for the admins, you often need extra content. Metrics, guidance, banners, whatever that make sense in a given app. I have 2 suggestions for this: Suggestion 1Adding 2 slots to the List Resource view to be able to support custom views. Something like this
class CustomerResource extends Resource
{
public static function headerView()
{
return view('admin.customers.header');
}
public static function footerView()
{
return view('admin.customers.footer');
}
} Suggestion 2Override the view, and do a callout to the tableview class CustomerResource extends Resource
{
public static function tableView()
{
return view('admin.customers.table');
}
} resources/views/admin/customers/table.blade.php <div>my custom header</div>
@include('filament::resources.pages.list-records')
<div>my custom footer</div>
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
This is already possible by overriding the It would be nice to have a header and footer view, you're right 👍 If you wanted to PR that it'd be great. |
Beta Was this translation helpful? Give feedback.
This is already possible by overriding the
$view
on the page component with a custom view - the code to render a table is very minimal.It would be nice to have a header and footer view, you're right 👍 If you wanted to PR that it'd be great.