CS 478 Reflection 3

Node

  1. I would say my experience with reusing the add book request handler logic was fairly straightforward and intuitive as both endpoints require validating the same fields, so I was able to simple reuse>
  2. This time around my experience with writing tests was much better than last time as I now had an idea of how to go about it. I think the biggest challenge was setting up predictable database state b>

React

  1. I integrated editing and deletion directly into the books table by adding “Edit” and “Delete” buttons for each row, i.e. each book in the record. Once you click the Edit button, a dialog box opens w>
  2. The most difficult part of implementing edit and delete in the UI was handling and managing states, especially for the dialog boxes. Keeping track of which book was being edited or deleted, having a>

Material UI

  1. I liked using Material UI’s API and visual design, it made the components look like a standard website as Material UI is so widely used. The structure of the API was consistent which made it easier >
  2. Refactoring my existing UI to use Material UI was a challenging task in the beginning, but it went easier than I expected. I just had to learn the syntax for the basic elements and then I was able t>
    3. [ Read 63 lines ]