How easy was it to reuse your add book request handler logic for your edit handler? What changes did you need to make and why?
It was quite easy, as said it was similar to the POST query but with an update instead. The only change I had to make was a new book schema so that it didn’t need every field as optional, as the user would likely only modify a few fields, not all.
What was your experience writing tests for your edit and delete endpoints?
This was very easy as again very similar to the other tests, I also already made the delete endpoint and tests within the last homework so I really only needed to test edit.
How did you integrate the book editing and deletion into your UI? Why did you choose the design you did?
I made it a form, it is the same format as Add Author/Book. I felt like this design is very intuitive, you can simply enter a Book ID and from there delete or edit the fields (shown as blank input) as needed.
What parts, if any, did you struggle with when implementing edit/delete in the UI?
I did not struggle, I just refactored what I had previously.
How did you feel about Material UI’s API and its look and feel?
I think it's cool, but it doesn't offer much, at least for our case with this homework. I was only able to utilize the nav bar and the table, as they do not have forms? I tried to look for a cool search or input box, but they just looked exactly the same as what I had so it seemed unnecessary. Not sure how this is like one of the biggest component libraries but seemed to offer very OK components.
How easy was it to refactor your existing UI to use Material UI?
It was easy, as I made small additions due to the lack of components that I would’ve wanted to use if they were available.