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

Update installation docs to mention testing

Browse Source 
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.
This commit is contained in:
Rodrigo Mesquita
2025-01-23 08:19:06 -03:00
committed by GitHub
parent dd4dd8a9cf
commit 0f08c340a9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/panels/docs/01-installation.md
+1 -1
View File
@@ -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
<?php