MVC Patern, Model in the View

Question

I work with PHP and understand how MVC works. There is one thing I am not sure about MVC. Is it a good practice to create a Model object directly in the View without passing it through the Controller because sometimes there is no need to process the Model in the Controller? Is there any disadvantage of doing that?

Answer 1

Its against the concept of MVC

Don't try to break the Architecture

Model - The lowest level of the pattern which is responsible for maintaining data.

View - This is responsible for displaying all or a portion of the data to the user.

Controller - Software Code that controls the interactions between the Model and View.

Reference Here

Answer 2

您的view仅显示结果，因此new Model()必须转到控制器，然后再传递给视图。

Answer 3

Yes - your view shouldn't need to rely on the Model staying the same.

Say for example, you're using a model which has ->forename and ->surname attributes. In your view, you just call these directly.

Then you decide later that you're going to add mutators and accessors (getters and setters) to your model, so you'll be using ->getForename() and ->getSurname() because you want to do some pre-processing on them to ensure the capitalisation is correct.

Now you need to go through all your controllers and views, because the usage needs to change.

If you'd instead just done all the model processing in your controller and then passed a standardised set of data to the view, you'd only need to update your controllers.

A View shouldn't expect anything of the Model, it should just require that it gets specific data from a Controller.

You could do something like this in your Controller:

$view = new View('my.file', [
    'user' => [
        'forename' => $user->forename,
        'surname' => $user->surname,
    ],
] );

this still gives you a $user['forename'] to use in your View, but now the format of that data is coming from the Controller, not the Model.