Home/ Questions/Q 8534081
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T10:06:45+00:00

I am battling to understand when I should create a new controller. Let’s say

  • 0

I am battling to understand when I should create a new controller.

Let’s say I have an application that maintains people records (Name, age etc)

I have a few views.
A view to show a list of people, which I can select to display.
A view to display detailed person information (view only)
A view to edit a person record
A view to add a person record
(Is Add and Edit usually one view, in MVC?)

At the moment, I have one controller. But is that right, or should I have a controller per view?
I’m worried my single controller is getting too big…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It is better to have a controller per resource (person in your case), not controller per view. So you are correct to have a PersonsController handling the list of persons, a person details and editing a person.

    • 0