Laracon, controller middleware, and permissions
Impossibile aggiungere al carrello
Puoi avere soltanto 50 titoli nel carrello per il checkout.
Riprova più tardi
Riprova più tardi
Rimozione dalla Lista desideri non riuscita.
Riprova più tardi
Non è stato possibile aggiungere il titolo alla Libreria
Per favore riprova
Non è stato possibile seguire il Podcast
Per favore riprova
Esecuzione del comando Non seguire più non riuscita
Laracon, controller middleware, and permissions
-
Letto da:
-
Di:
A proposito di questo titolo
In this episode, Michael and Jake kick things off with some Laracon travel talk, sharing their hotel plans, coffee quests, and even jokes about pillow fights at the conference hotel. Michael reveals his precise coffee scouting for the Vib by Best Western hotel, determined not to survive three days on Starbucks alone.
- Should you define middleware in a controller’s constructor?
Michael explains why he avoids it - preferring to keep all middleware in route definitions for better visibility and maintainability. Jake explores the pros and cons and why he’s still tempted to use it for certain edge cases. - Dynamic permissions vs. static definitions:
We switch gears to talk about the balance between flexibility and clarity when defining permissions for applications, especially when it comes to handling user roles, teams, and complex business rules.
Mentioned in this episode:
- Laracon US travel plans
- Vib by Best Western (the hotel coffee and tacos!)
- Laravel middleware usage
- Permission handling in apps
- Travel gear for developers on the go
Ancora nessuna recensione