It’s worse than the hack we called “disgusting,” in terms of software design. Why didn’t we make that form a separate component? Not doing that is by far the biggest shortcut we took over the course of this module. (That’s why we drew a box around it in the user interface!) At the very least, we hope you see that the Add Expense form really should be its own, separate component. You’ll see that you can decompose our app further, into smaller pieces, than we’ve done so far. Here’s how everything comes together, with the createExpense and updateExpense events you’re wiring up later.īut, if you look at the app on screen, what do you see? What you should see, and what you’ll eventually see everywhere you look, is that the app breaks down into many more components. If you take a look at our little expenses app in source code form, and list the separate code artifacts, you’ll come up with something like the following.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |