Summary

This chapter was entirely dedicated to Angular forms. We started clarifying what a form actually is and enumerated the features it needs to have in order to fulfill its duties, grouping them into two main requirements: providing a good user experience and properly handling the submitted data.

We then turned our focus to the Angular framework and to the two form design models it offers: the Template-Driven approach, mostly inherited from AngularJS, and the Model-Driven or Reactive alternative. We took some valuable time to analyze the pros and cons provided by both of them, and then we performed a detailed comparison of the underlying logic and workflow. At the end of the day, we chose to embrace the Reactive way of doing things, as it gives more control to the developer and enforces a more consistent separation of duties between the Data Model and the Form Model.

Right after that, we went from theory to practice by testing our acquired knowledge on our client app's QuizEditComponent...