Controller methods convention for two routes that display the same information

I like dhh's advice:

...whenever I have the inclination that I want to add a method on a controller that’s not part of the default five or whatever REST actions that we have by default, make a new controller!

and Taylor Otwell's

... a lot of people's architectural problems would be solved by having more controllers.

Maybe a UserOffersController, so you could show offers by whichever user you want.

Personally, I like the ADR approach. Create action specific controllers and just have an __invoke method for each. You end up with a lot of controllers, but you have a clear single purpose for each and you end up with fewer dependencies per controller.

@DEMERS94 - I've been doing whatever I can to use only the "normal" rest methods in my controllers and to, instead of making up new methods, create more controllers. Like @clay mentioned, UserOffersController or something of the like is where I'd be going with it. Then you can keep with only using index/show/create/store/edit/update/destroy.

Btw - after a few months of striving for this, I really like the way things are turning out in my projects. Things seem way less mentally taxing this way - not having to constantly reverse engineer controllers I've built to re-figure out how to use them.

@clay - This __invoke strategy that you invented... I would love to see an example of it if you wouldn't mind posting one. I have never seen that or thought about doing it. It sounds interesting. Also, if you're thinking about claiming that you did not invent __invoke, it's too late. I already made a note that you invented it. Way to go!

I'd do a new controller as mentioned, but probably name it OwnerOffersController since it's a bit more clear semantically.

Thank you @clay, @goatshark and @Cronix for the feedback!

I like UsersOffersController, makes more sense than OwnOffersControllers. OwnerOffersController is good too.

@clay, what is that _invoke() approach?

@goatshark If you google 'action domain responder' you'll find some examples. There's many blog posts and several videos about it from various conferences.

Also, @martinbean blogged about implementing the full ADR pattern in laravel.

I don't implement the full pattern, but i do incorporate several of the key concepts in my own apps.

@clay Thanks for the direction and resources.

@clay Thanks for the mention :)

@Demers94 It definitely makes sense to have two controllers, each with an index() method. If a user is able to view their own job “offers” in some sort of account area, then you could maybe use name-spacing:

Route::get('/', 'JobOfferController@index');

Route::group(['middleware' => 'auth'], function () {
    Route::get('account/offers', 'Account\JobOfferController@index');
});