When do you need to inherit Controller?

Question

Laravel

Hello.
I periodically create classes that are neither models nor controllers - i.e. they just contain all sorts of utility functions.
But by inertia, I create them through artisan make:controller :-) and, accordingly, it inherits the Controller class
. And I suspect that this is not always necessary ))
What do I get from the Controller class in my controllers?
For example, dependency injection into a function - is it from him?
How to understand where I need it and where not?
Thank you.

Answer 1

I periodically create classes that are neither models nor controllers - i.e. they just contain all sorts of utility functions.

You create service classes.
Work with requests and responses, sessions, cookies, etc.
No, it works throughout the Laravel application. You can define your class and use DI there.
If your class does not contain work with requests and responses, then it makes no sense to inherit from Controller.
You can poke around inside the controller's base class to see what it contains. It won't be redundant.