Laracon, controller middleware, and permissions
Échec de l'ajout au panier.
Veuillez réessayer plus tard
Échec de l'ajout à la liste d'envies.
Veuillez réessayer plus tard
Échec de la suppression de la liste d’envies.
Veuillez réessayer plus tard
Échec du suivi du balado
Ne plus suivre le balado a échoué
Laracon, controller middleware, and permissions
-
Narrateur(s):
-
Auteur(s):
À propos de cet audio
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
Ce que les auditeurs disent de Laracon, controller middleware, and permissions
Moyenne des évaluations de clientsÉvaluations – Cliquez sur les onglets pour changer la source des évaluations.
Il n'y a pas encore de critiques pour ce titre.