Yes, I reused most of the APIs of the add book for the edit book mostly because of the endpoints needing the same inputs and forms, aswell as validation. So I just reused that part. The parts I needed to change was making it update instead of insert, which means i needed to check if the book id exists first before making any changes so it doesnt make a new book, and returns a 404 error.
I integrated the book editing and deletion into the UI by using a modal pop up style (or in this case a Material UI Dialog) because I feel like it makes the most sense for this type of work, and also that I am used to making modals back in CS375 although it is a bit different. This is also cause it keeps everything in the same page so there is no extra routes or potential problems that come out with that. Some issues I faced was making sure that when I clicked on the button to edit and delete to make sure the right book was being tracked and filling the edit with the corresponding data. There were some problems where it didnt find books that existed or just didnt find specific forms that was annoying.
The initial Material UI stuff was confusing with all the components and patterns I needed to add and honestly I had to get some help from an LLM in some area, but once I started to understand I think its alot more straightforward and honestly feels alot consistent without having to do any CSS edits (granted my front end is still barebones). Refactoring though was a bit tough, I never used Material UI and the website didnt really help me that much so I had to resort to videos and some LLM assistance but after a bit of understanding it was moving alot more smoother. Alot of the logic didnt need to change it was just changing mechanical stuff that took a bit.