I integrated edit and deletion onto the main BooksTable page of the website. To me, it just made sense that the edit/deletion field would exist alongside the full view of the books table. A user needs to see the whole table if they want to edit or delete something. Deleting was pretty straightforward, but I had struggles with the edit interface. I wanted the interface to be a pop-up screen, and it took a lot of trial+error to figure out. I could not find a way to add a label to the dropdown menus to change the author and genre and didn't spend more time on that.
It was not easy refactoring, but the challenge of learning Materials UI was fun. As I mentioned in the previous question, I spent the most time trying to get the edit interface to work. While Materials UI provides greater flexibility for making UI fancy and pretty, it comes at the cost of complexity.
Not that difficult adding the editting component. I mostly based it off my previous endpoints, which helped a lot. The unit test was also based on my previous tests, and wasn't that big of a struggle.