Database
Blade
Architecture
Last updated
2 years ago.
You don't want to duplicate code. That makes sense, you'd have to change multiple places if the code needed to change.
The way to solve for this is not to have controllers interact with one another. It's to create an object that is responsible for something that you need, and injecting it into each controller that you need. In this way you can use the functionality all over the place.
Last updated
2 years ago.
ShawnMcCool said:
create an object that is responsible for something that you need
Like a global variable?
Last updated
2 years ago.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast