Controllers in laravel

Question

I would like to know when it's the best to create a controller.

I mean why can't we just use 1 controller for all our functions.

For example I have this controller called forumcontroller

why can't I just put all my functions in that controller and then do something like.

forumcontroller@function1

forumcontroller@function2

forumcontroller@function3

When is it best to create a new one?

The point is to keep things simple and readable. But if you have 20 different forum-related methods, and you ask 20 different programmers, you're going to get wildly differing opinions on where and how you should stick all of them. This question is inevitably opinion-based. That's not to say it's a bad question - it's really a good one. Just not suitable for SO. — Joel Hinz
– Joel Hinz, Commented Oct 4, 2016 at 11:52
It is not about Laravel is about MVC good topic also on SO stackoverflow.com/questions/5735761/… — SergkeiM
– SergkeiM, Commented Oct 4, 2016 at 11:53
@Froxz Thanks for the extra information, I'll take a look at that. — Kevin.a
– Kevin.a, Commented Oct 4, 2016 at 12:17

Komal · Accepted Answer · 2016-10-04 11:57:32Z

1

It's a good practice to crate different controllers for different module like UserController for user module, ForumController for forum module, BookingController for booking module etc.. It's easy to handle your code..

answered Oct 4, 2016 at 11:57

Komal

2,7364 gold badges26 silver badges33 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Mahfuzul Alam · Accepted Answer · 2016-10-04 12:09:30Z

1

It's all about readability, simplicity, refactoring and design patterns.

answered Oct 4, 2016 at 12:09

Mahfuzul Alam

3,17716 silver badges15 bronze badges

Collectives™ on Stack Overflow

Controllers in laravel

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related