Controller pattern for route handlers in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Controller pattern in Express route handlers?

It is a way to organize code by separating route logic into controller functions. Controllers handle requests and responses, keeping routes clean and focused.

beginner

Why use controllers instead of writing all logic inside routes?

Controllers make code easier to read, test, and maintain by separating concerns. Routes just direct traffic, controllers do the work.

beginner

How do you define a controller function in Express?

A controller is a function that takes (req, res) parameters and handles the request, like sending a response or calling next().

beginner

Example: What does this controller do?
<pre>const getUser = (req, res) => { res.send('User info'); };</pre>

It sends a simple text response 'User info' when called. This controller handles a request by replying with user information.

beginner

How do you connect a controller to a route in Express?

You import or define the controller function and pass it as the second argument to the route method, like app.get('/path', controllerFunction).

What is the main role of a controller in Express?

A Handle the logic for requests and responses

B Define the URL paths for routes

C Manage database connections

D Serve static files

Controllers handle the logic for processing requests and sending responses.

Where should you put the code that sends a response to the client?

A In the middleware before the route

B Inside the route definition only

C Inside the controller function

D In the server setup file

Controllers are responsible for sending responses to keep routes clean.

How do you use a controller in an Express route?

A Pass the controller function as the route handler

B Call the controller inside the route handler manually

C Controllers are not used with routes

D Controllers replace the Express app

You pass the controller function directly as the route handler.

Which of these is a benefit of using controllers?

A Automatically creates routes

B Makes the server run faster

C Handles user authentication

D Improves code organization and readability

Controllers help organize code and make it easier to read and maintain.

What parameters does a typical Express controller function receive?

A app and router

B req and res

C next and error

D url and method

Controllers receive the request (req) and response (res) objects.

Explain how the Controller pattern helps organize Express route handlers.

Think about how splitting tasks makes code easier to manage.

Describe the steps to create and use a controller function in an Express app.

Focus on function creation and connecting it to routes.

Practice

1. What is the main purpose of using the controller pattern in Express route handlers?

easy

A. To separate route logic from routing setup for better organization

B. To combine all route handlers into a single file

C. To directly write SQL queries inside route handlers

D. To avoid using middleware functions in routes

Solution

1. Step 1: Understand the controller pattern concept

   The controller pattern means moving the logic that handles requests out of the route definitions into separate functions or files.

2. Step 2: Identify the benefit of separation

   This separation improves code organization, making it easier to read and maintain.

3. Final Answer:

   To separate route logic from routing setup for better organization -> Option A

4. Quick Check:

   Controller pattern = separation of concerns [OK]

Hint: Controllers keep route files clean and logic separate [OK]

Common Mistakes:

• Thinking controllers combine all routes in one file
• Believing controllers write database queries directly
• Confusing controllers with middleware avoidance

2. Which of the following is the correct way to import and use a controller function named getUser in an Express route?

easy

A. router.get('/user', getUser());

B. router.get('/user', () => getUser);

C. router.get('/user', getUser => {});

D. router.get('/user', getUser);

Solution

1. Step 1: Understand how to pass controller functions

   In Express, route handlers expect a function reference, not the result of calling the function.

2. Step 2: Identify correct syntax

   Passing getUser without parentheses passes the function itself. Using parentheses calls it immediately, which is incorrect here.

3. Final Answer:

   router.get('/user', getUser); -> Option D

4. Quick Check:

   Pass function reference without () [OK]

Hint: Pass controller as function reference, no parentheses [OK]

Common Mistakes:

• Calling the controller function immediately with ()
• Using arrow functions incorrectly wrapping the controller
• Returning the function instead of calling it

3. Given this controller function and route setup, what will be the response when a GET request is made to /hello?

const sayHello = (req, res) => {
  res.send('Hello from controller!');
};

router.get('/hello', sayHello);

medium

A. Hello from controller!

B. Error: sayHello is not a function

C. No response, request hangs

D. 404 Not Found

Solution

1. Step 1: Analyze the controller function behavior

   The sayHello function sends a plain text response 'Hello from controller!' when called.

2. Step 2: Check route setup correctness

   The route uses sayHello correctly as the handler for GET requests to '/hello'.

3. Final Answer:

   Hello from controller! -> Option A

4. Quick Check:

   Controller sends response text [OK]

Hint: Controller sends response, route calls it correctly [OK]

Common Mistakes:

• Forgetting to call res.send inside controller
• Passing controller incorrectly causing runtime error
• Misreading route path causing 404

4. Identify the error in this Express controller pattern usage:

const userController = {
  getUser: (req, res) => {
    res.json({ name: 'Alice' });
  }
};

router.get('/user', userController.getUser());

medium

A. res.json should be res.send

B. Missing import statement for router

C. Calling userController.getUser() immediately instead of passing function

D. Route path should be '/users' not '/user'

Solution

1. Step 1: Check how controller function is passed

   The code calls userController.getUser() immediately, which runs the function and passes its result, not the function itself.

2. Step 2: Understand correct usage

   Express expects a function reference as the route handler, so it should be userController.getUser without parentheses.

3. Final Answer:

   Calling userController.getUser() immediately instead of passing function -> Option C

4. Quick Check:

   Pass function reference, not call it [OK]

Hint: Don't add () when passing controller to route [OK]

Common Mistakes:

• Calling controller function instead of passing it
• Confusing res.json and res.send (both valid here)
• Assuming route path naming causes error

5. You want to organize your Express app using the controller pattern. You have multiple routes for users: getUser, createUser, and deleteUser. Which approach best follows the controller pattern for clean code?

hard

A. Put all route definitions and logic inside a single routes.js file without controllers

B. Define all user-related functions in a separate userController.js file and import them in the router file

C. Write all user route handlers directly inside the main app.js file

D. Use inline anonymous functions for each route in the router file

Solution

1. Step 1: Understand controller pattern best practice

   Controllers group related route logic into separate files or modules to keep code organized and reusable.

2. Step 2: Evaluate options for clean code

   Defining all user-related functions in a dedicated userController.js file and importing them into the router file follows the pattern well.

3. Final Answer:

   Define all user-related functions in a separate userController.js file and import them in the router file -> Option B

4. Quick Check:

   Separate logic into controller files [OK]

Hint: Group related handlers in controller files, import in routes [OK]

Common Mistakes:

• Putting all logic in main app file making it messy
• Mixing routes and logic in one file without separation
• Using anonymous functions inline reduces reusability