Refactor Laravel Permissions into Policies: Our Small Example
I want to quickly show an example of a small refactoring inside our LaravelDaily.com permissions when while adding a new feature of Team Plans, "along the way" we decided to refactor the code to Policies, for future re-use.
- - - -
Support the channel by checking out my products:
My Laravel courses: https://laraveldaily.com/courses
Laravel QuickAdminPanel: https://quickadminpanel.com
Livewire Kit Components: https://livewirekit.com
- - - -
Other places to follow:
My weekly Laravel newsletter: https://us11.campaign-archive.com/hom...
My personal Twitter: / povilaskorop
![[09/10] Laravel Travel API: Laravel Pint and Larastan](https://images.videosashka.com/watch/iVhOVxEyjFE)
![[07/10] Laravel Travel API: Admin Endpoint to Create Tour](https://images.videosashka.com/watch/glDKQxYSJlw)
![[03/10] Laravel Travel API: Public Endpoint for Tours with Tests](https://images.videosashka.com/watch/YU-26bqHP7U)
![[02/10] Laravel Travel API: Public Endpoint with Pagination and Tests](https://images.videosashka.com/watch/fJYJMFr6FuE)
![[01/10] Laravel Travel API: DB Schema - Models and Migrations](https://images.videosashka.com/watch/9aIVmiL3Xks)
