opensource/filament
3
0
Fork 0
mirror of https://github.com/filamentphp/filament.git synced 2026-09-24 15:42:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add note about multiple paginators with custom tables (#19279)

Browse Source 
* Add note about multiple paginators with custom tables

* chore: fix code style

* Update 09-custom-data.md

---------

Co-authored-by: cheesegrits <cheesegrits@users.noreply.github.com>
Co-authored-by: Dan Harrin <git@danharrin.com>
This commit is contained in:
Hugh Messenger
2026-02-19 10:06:07 +00:00
committed by GitHub
co-authored by cheesegrits Dan Harrin
parent ff83c96d80
commit a32dd9efee
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/tables/docs/09-custom-data.md
+4
View File
@@ -329,6 +329,10 @@ In this example, the `forPage()` method is used to paginate the data. This proba
It might seem like Filament should paginate the data for you, but in many cases, it's better to let your data source—like a custom query or API call—handle the pagination instead.
</Aside>
<Aside variant="warning">
If you have multiple custom tables on a page and are using the `queryStringIdentifier('customIdentifier')` method to distinguish them, you will need to add an `options` argument to the `LengthAwarePaginator` with the `pageName`, like `options: ['pageName' => 'customIdentifierPage']`. Note that adding the `Page` suffix to your custom identifier is required here.
</Aside>
## Actions
[Actions](actions) in the table work similarly to how they do when using [Eloquent models](https://laravel.com/docs/eloquent). The only difference is that the `$record` parameter in the action's callback function will be an `array` instead of a `Model`.