From 0f08c340a95d34ae15f3bb0804e2609f929bbfe9 Mon Sep 17 00:00:00 2001 From: Rodrigo Mesquita <30835404+rrmesquita@users.noreply.github.com> Date: Thu, 23 Jan 2025 08:19:06 -0300 Subject: [PATCH] Update installation docs to mention testing When testing a Laravel app, the application environment automatically switches to `testing`, so if `canAccessPanel` is not implemented, tests will fail (as they should) but the developer might not know why instantly. Feel free to keep it shorter if you think this change don't add much value. --- packages/panels/docs/01-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/panels/docs/01-installation.md b/packages/panels/docs/01-installation.md index 52e0e8bba2..203eedd3b0 100644 --- a/packages/panels/docs/01-installation.md +++ b/packages/panels/docs/01-installation.md @@ -86,7 +86,7 @@ You should also consider optimizing your Laravel app for production by running ` ### Allowing users to access a panel -By default, all `User` models can access Filament locally. However, when deploying to production, you must update your `App\Models\User.php` to implement the `FilamentUser` contract — ensuring that only the correct users can access your panel: +By default, all `User` models can access Filament locally. However, when testing or deploying to production, you must update your `App\Models\User.php` to implement the `FilamentUser` contract — ensuring that only the correct users can access your panel: ```php