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 fairly easy to reuse my add book request handler logic for the edit handler since much of the logic was similar. The main change I made was adding support for partial updates, since when editing, the user does not need to update every field.
What was your experience writing tests for your edit and delete endpoints?
Writing tests was helpful and allowed me to catch issues such as partial updates and other errors.
How did you integrate the book editing and deletion into your UI? Why did you choose the design you did?
I integrated book editing and deletion into my UI by adding another column to the book list with buttons representing edit and delete actions for each row. I chose this design because it is simple and does not require navigating to another page.
What parts, if any, did you struggle with when implementing edit/delete in the UI?
The hardest part was keeping the front end and back end in sync after editing and deleting.
How did you feel about Material UI's API and its look and feel?
I felt that it was easy to use since there were many components that were easy to integrate into my code, and it made the UI look more polished without requiring custom CSS.
How easy was it to refactor your existing UI to use Material UI?
Refactoring went pretty smoothly since many HTML elements I used mapped directly to Material UI components.