Lesson 4 - E-shop in PHP - Controller action design
In the previous lesson, E-shop in PHP - App folder and making the project runnable, we added the last couple of changes needed to our project directory structure and made the project functional again. Although the new architecture makes the project much clearer, the framework still lacks a lot a functionality needed to build a large application. Mainly, our framework suffers from these 2 issues:
- Each controller can only perform a single action (the index() method), which leads to either long methods or the exponential growth of the number of controllers alongside the application's complexity. Also, there's no way for a controller to work with an API, e.g. for AJAX.
- Real commercial applications are based on forms. Up until now, we've written all of our forms manually, where the templates weren't very pretty (they were large and had us fill the data in manually). We had to manually write in a validation for every single form and implement code that retrieved $_POST data over and over again. This way, if we gave it enough time, we'd type ourselves to death.
Today's tutorial is about modifying the controller's design.
...End of the preview...
You've come here and that's great! We believe that the first lessons showed you something new and useful
Do you want to continue the course? Go to the premium section.
Buy this course
Before buying this article, you have to buy the previous one
- Unlimited and permanent access to individual lessons.
- High quality IT knowledge.
- Skills to help you get your dream and well-paid job.
Requested article covers this content:
In this tutorial, we'll focus on the last couple of problems in our framework, which are controller actions, the lack of an API, and forms.
You gain credits by supporting our network. This is done by sending a helpful amount of money to support the site, or by creating content for the network.