Member Since 3 Years Ago
1,190 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Started a new Conversation L8, Jetstream, Spatie/laravel-permission - Guard Switching To Sanctum
Laravel 8 Jetstream (Teams and API features disabled) Spatie's laravel-permissions package (Role and Permission models come from here)
When writing a test for creating a Role, a Permission created in the testing setup is given the 'web' guard_name as expected however when I'm then 'actingAs()' a user and try to create a Role within a controller, the 'sanctum' guard_name is automatically applied to the new Role. If I then try to $role->syncPermissions() with the permissions I created in the test setup, I get an error about a guard mismatch.
composer remove laravel/sanctum
I then removed the reference to Sanctum in the middleware for the route (from 'auth:sanctum' to just 'auth').
Does anyone foresee any issues with this method? I know I could manually set a 'guard_name' for every Permission/Role I create but I wanted to avoid this if I could. I do wonder if simply changing the route middleware from 'auth:sanctum' to just 'auth' would have solved it, without having to remove Sanctum entirely?