merge commit branch1

[AnnabellePLS]

merge

Summary by CodeRabbit

• New Features
  • Task management REST API is now available with complete CRUD functionality. Users can retrieve all tasks, create new tasks, fetch specific tasks by ID, update existing tasks, and delete tasks via the /api/v2/tasks endpoint.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new Express.js task manager API is established with server initialization in app.js, CRUD controller handlers in controllers/tasks.js, and route definitions in routes/tasks.js. The server listens on port 3000 with endpoints for managing tasks via REST conventions.

Changes

Cohort / File(s)	Summary
Server Setup 03-task-manager/starter/app.js	Replaced console.log with complete Express server initialization, including middleware for JSON parsing, a /hello route, and task router mounted at /api/v2/tasks listening on port 3000.
Task API Layer 03-task-manager/starter/controllers/tasks.js, 03-task-manager/starter/routes/tasks.js	New controller module exports five CRUD handlers (getAllTasks, createTask, getTask, updateTask, deleteTask); new router module wires them to REST endpoints (GET /, POST / for collection; GET /:id, PATCH /:id, DELETE /:id for individual tasks).

Sequence Diagram

sequenceDiagram
    Client->>app.js: HTTP Request
    app.js->>+routes/tasks.js: Route matching
    routes/tasks.js->>controllers/tasks.js: Invoke handler
    controllers/tasks.js->>controllers/tasks.js: Process request
    controllers/tasks.js-->>routes/tasks.js: Return response
    routes/tasks.js-->>-app.js: Send to client
    app.js-->>Client: HTTP Response

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A task manager springs to life,
With routes that hop and controllers that thrive,
REST endpoints configured with care,
The server bounces with flair—
Port 3000 awaits, tasks to share! 🚀

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'merge commit branch1' is vague and generic, using non-descriptive language that doesn't convey meaningful information about the actual changes (Express server setup, task controllers, and routing infrastructure).	Replace with a descriptive title that summarizes the main change, such as 'Add task manager Express server setup with controllers and routes' or 'Set up Express API with task management endpoints'.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@03-task-manager/starter/app.js`:
- Line 19: The call to app.listen executes console.log immediately instead of as
the bind callback; change the second argument to a callback function so logging
runs after the server successfully binds (replace the direct console.log(...)
invocation passed into app.listen with a function wrapper such as an arrow or
named function that calls console.log with the port variable), locating the call
to app.listen and adjusting it accordingly.

🧹 Nitpick comments (1)

03-task-manager/starter/app.js (1)

17-17: Make the port configurable via process.env.PORT.
Helps with deployment platforms that inject a port.

♻️ Suggested change

-const port = 3000
+const port = process.env.PORT || 3000

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Wrap console.log in a callback for app.listen.
Passing console.log(...) executes immediately and doesn’t log on successful bind.

✅ Suggested fix

-app.listen(port, console.log(`server is listening on port ${port}...`))
+app.listen(port, () => console.log(`server is listening on port ${port}...`))

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	app.listen(port, console.log(`server is listening on port ${port}...`))
	app.listen(port, () => console.log(`server is listening on port ${port}...`))

🤖 Prompt for AI Agents

In `@03-task-manager/starter/app.js` at line 19, The call to app.listen executes
console.log immediately instead of as the bind callback; change the second
argument to a callback function so logging runs after the server successfully
binds (replace the direct console.log(...) invocation passed into app.listen
with a function wrapper such as an arrow or named function that calls
console.log with the port variable), locating the call to app.listen and
adjusting it accordingly.