Initial set-up

Here we destructure but would it be easier to pass this entire object into Book.create()?
We could just set default values for borrower dateBorrowed dateBorrowed in the model.

Then this would be a bit cleaner and look like Book.create(req.body, imagePath)

This casing feels wrong, what is the convention for casing in MongoDB?

The two options for the form:

• display as a modal
• only displayed on page when button is clicked

Include the following fields:

• Title (text field)
• Author (text field)
• Genre (dropdown)
• Image?
• Editable?
• delete button (or archive maybe?)

Styling

Creating this object should probably live in the model

We use this check 3 times in this file.

It would be better to create a method for this check.
isValidId(id) would be easier to read and reuse

Related to appending information from form to the list (library)
Books show as narrow card on the page with book title, author name and when clicked on more information is shown (modal?).

Styling

We shouldn't throw 500, it should be for unhandled errors

Store locally for the time being.

Should we try to delete a book we don't know exists?

In my mind, the flow should be.

• Verify id is valid
• Verify user has a book with this id
• Delete the book

Then we could reformat like this.

const deleteBook = async (req, res) => {
  const { id } = req.params;

  if (!isValidId(id)) {
      return res.status(404).json({ error: "No such book in your library!" });
  } else if (Book.hasBook(id) {
      const book = await Book.findOneAndDelete({ _id: id });
      res.status(200).json(book);
  } else {
      return res.status(404).json({ error: "No such book in your library!" });
}

This logic shouldn't live here.

it would be much easier to read if we had.

const imagePath = getImagePath(req.file)