Intermediate Bonus Phase Two - Routes For Insects

Understand the Problem

We want to mirror the same functionality we built for Trees onto Insects. This includes:

• Listing all insects, returning id, name, millimeters, sorted by millimeters.
• Fetching a single insect by id.
• Creating a new insect record.
• Deleting an insect by id.
• Updating an insect’s fields, ensuring id matches in URL/body.
• Searching insects by name (using a “like” query) if desired.

Devise a Plan

1. Create or open insects.js in server/routes.
2. Implement the routes: GET /insects, GET /insects/:id, POST /insects, DELETE /insects/:id, PUT /insects/:id, optional GET /insects/search/:term.
3. Use the same Sequelize methods (findAll, findByPk, create, destroy, save) as in the Trees routes.

Carry Out the Plan (Solution)

File Name & Location: server/routes/insects.js

// Example skeleton (simplified):
// GET /insects
//   Insect.findAll({ attributes: ['id','name','millimeters'], order: [['millimeters','ASC']] })
// GET /insects/:id
//   Insect.findByPk(id)
// POST /insects
//   Insect.create(body)
// DELETE /insects/:id
//   Insect.destroy({ where: { id } })
// PUT /insects/:id
//   Check param/body match
//   Find insect, update fields, save
// (Optional) GET /insects/search/:term (like query by name)
    

Expected Input: Various HTTP methods with JSON bodies or URL params.

Expected Output: Insect data in JSON or error messages for invalid requests.

Elementary (Basic) Approach

• Simple replication of the same logic from trees.js, changing attribute names to match insects’ fields (e.g., name, description, fact, territory, millimeters).

Advanced Approach

• Additional validations (e.g., millimeters > 0), unique name constraints, etc.

Step-by-Step Directions:

1. Create the route file insects.js if it doesn’t exist.
2. Import Insect from the models folder.
3. Implement each route with the standard Sequelize CRUD pattern.
4. Test with Postman or your test suite to confirm functionality.

Explanations & Analogies: The Insects resource is analogous to Trees; the only difference is which fields the database stores. The CRUD logic is effectively the same.

Real World Example: If the system also needs insects data for a nature or scientific study app, having parallel routes is practical.

Look Back

Confirm your Insects data is accessible and modifiable just like Trees. If your application uses the many-to-many relationships, these endpoints are crucial for referencing insect IDs.