Level 30
Moving to a model seems more appropriate since this helper interacts with database. Utilize local scope: https://laravel.com/docs/13.x/eloquent#local-scopes
1 like
Apr 2, 2026
3
Level 2
Controller's helper fn
Where should i keep the helper fn that fetches some data from a particular db table and is then used extensively across only two controller classes? Should i keep it as a private member function in both controllers and then invoke it in other member functions as:
$result = this->myFn();
Or should I move it to a model, mark it as static and then in my controllers invoke it as:
$result = SomeModel::myFn();
Level 4
Definitely don't duplicate the code in both controllers keep it DRY.
Since it involves fetching data, the logic belongs in the Model. Using a Local Scope is the most idiomatic Laravel way to handle this. However, if it’s a more specialized fetch that doesn’t fit a scope, a static method on the model is a solid choice. Just keep the database logic out of the controllers.
1 like
Level 122
another option is a trait, used in both places
1 like
Please or to participate in this conversation.