Validation error response formatting in Express - Step-by-Step Execution

Concept Flow - Validation error response formatting

Receive HTTP Request

↓

Validate Input Data

↓

Process Request

↓

Send Success

↓

End

The server receives a request, checks the input data, and either processes it or sends back a formatted error response.

Execution Sample

Express

app.post('/user', (req, res) => {
  const { name, age } = req.body;
  if (!name) {
    return res.status(400).json({ error: 'Name is required' });
  }
  res.json({ message: 'User created' });
});

This code checks if the 'name' field is missing and sends a formatted error response if so.

Execution Table

Step	Action	Input Data	Validation Result	Response Sent
1	Receive request	{ age: 25 }	Not validated yet	No response yet
2	Check if name exists	{ age: 25 }	Name missing	400 status with { error: 'Name is required' }
3	Stop processing	N/A	Validation failed	Error response sent, request ended

💡 Validation failed because 'name' is missing, so error response is sent and processing stops.

Variable Tracker

Variable	Start	After Step 2	Final
req.body.name	undefined	undefined	undefined
validationResult	undefined	false (name missing)	false (validation failed)
response.statusCode	undefined	400	400

Key Moments - 2 Insights

Why does the server send a 400 error instead of processing the request?

Because the validation check at step 2 finds the 'name' field missing, so it sends a 400 error response immediately as shown in the execution_table row 2.

What happens if the 'name' field is present?

If 'name' is present, validation passes and the server proceeds to process the request and send a success response, which is not shown here but would be after step 2.

Visual Quiz - 3 Questions

Look at the execution table, what response is sent at step 2?

A 500 Internal Server Error

B 200 OK with success message

C 400 status with error message

D No response sent yet

💡 Hint

Check the 'Response Sent' column at step 2 in the execution_table.

At which step does the validation fail?

A Step 1

B Step 2

C Step 3

D Validation never fails

💡 Hint

Look at the 'Validation Result' column in the execution_table.

If the input had { name: 'Alice', age: 25 }, how would the response change?

A Sends 200 success message

B Still sends 400 error

C Sends 404 not found

D Sends 500 server error

💡 Hint

Refer to the key_moments explanation about what happens if 'name' is present.

Concept Snapshot

Validation error response formatting in Express:
- Receive request and extract input
- Check required fields (e.g., name)
- If missing, send res.status(400).json({ error: 'message' })
- Stop further processing
- If valid, continue and send success response

Full Transcript

In Express, when a request comes in, the server checks if the input data meets requirements. For example, it verifies if the 'name' field exists. If the field is missing, the server immediately sends a 400 status code with a JSON error message and stops processing. This prevents invalid data from being processed. If the input is valid, the server continues to handle the request and sends a success response. This flow ensures clear communication to the client about what went wrong or right.

Practice

1. What HTTP status code is typically used to indicate validation errors in an Express API response?

easy

A. 400 Bad Request

B. 200 OK

C. 500 Internal Server Error

D. 404 Not Found

Solution

1. Step 1: Understand HTTP status codes for client errors

   Validation errors occur when the client sends bad data, so a 4xx code is appropriate.

2. Step 2: Identify the specific code for bad input

   400 Bad Request is the standard code for invalid input from the client.

3. Final Answer:

   400 Bad Request -> Option A

4. Quick Check:

   Validation errors use 400 status [OK]

Hint: Validation errors always use 400 status code [OK]

Common Mistakes:

• Using 200 OK for validation errors
• Confusing 500 Internal Server Error with validation errors
• Using 404 Not Found for input mistakes

2. Which of the following is the correct way to send a JSON validation error response in Express?

easy

A. res.status(400).send('Validation failed')

B. res.json({ error: 'Validation error' })

C. res.status(400).json({ errors: [{ msg: 'Invalid input' }] })

D. res.sendStatus(200)

Solution

1. Step 1: Use status 400 for validation errors

   The response must have status 400 to indicate a client error.

2. Step 2: Format the response as JSON with an errors array

   Returning an object with an errors array containing message objects is the standard pattern.

3. Final Answer:

   res.status(400).json({ errors: [{ msg: 'Invalid input' }] }) -> Option C

4. Quick Check:

   Use res.status(400).json with errors array [OK]

Hint: Use res.status(400).json({ errors: [...] }) for validation errors [OK]

Common Mistakes:

• Sending plain text instead of JSON
• Omitting the status code
• Using 200 status for errors

3. Given this Express route snippet, what will be the JSON response if the input validation fails?

app.post('/user', (req, res) => {
  const errors = [];
  if (!req.body.email) errors.push({ msg: 'Email is required' });
  if (errors.length > 0) {
    return res.status(400).json({ errors });
  }
  res.send('User created');
});

medium

A. {"error":"Email missing"} with status 400

B. {"errors":[{"msg":"Email is required"}]} with status 400

C. "User created" with status 200

D. Empty response with status 400

Solution

1. Step 1: Check validation logic for missing email

   If email is missing, an error object with msg 'Email is required' is added to errors array.

2. Step 2: Return JSON with errors array and status 400

   Since errors array is not empty, the response sends status 400 and JSON containing errors array.

3. Final Answer:

   {"errors":[{"msg":"Email is required"}]} with status 400 -> Option B

4. Quick Check:

   Validation fails -> 400 + errors array JSON [OK]

Hint: Errors array with messages sent with 400 status [OK]

Common Mistakes:

• Returning success message despite errors
• Wrong JSON key like 'error' instead of 'errors'
• Not setting status 400

4. Identify the bug in this Express validation error response code:

if (!req.body.name) {
  res.json({ errors: [{ msg: 'Name is required' }] });
  res.status(400);
}

medium

A. Status code must be set before sending response

B. Response should use res.send instead of res.json

C. Errors array should be a string, not an object

D. No bug, code is correct

Solution

1. Step 1: Check order of status and response methods

   res.status(400) must be called before sending the response to set status properly.

2. Step 2: Identify that res.json sends response immediately

   Calling res.json first sends the response with default status 200, so status(400) after has no effect.

3. Final Answer:

   Status code must be set before sending response -> Option A

4. Quick Check:

   Set status before res.json/send [OK]

Hint: Call res.status before res.json/send [OK]

Common Mistakes:

• Setting status after sending response
• Using res.send instead of res.json (not a bug but less clear)
• Not sending any status code

5. You want to send multiple validation errors in a consistent format in Express. Which code snippet correctly formats and sends these errors with HTTP 400 status?

const errors = [
  { field: 'email', message: 'Invalid email' },
  { field: 'password', message: 'Password too short' }
];
// What is the correct response code?

hard

A. res.status(400).json({ errorMessages: errors })

B. res.json({ errors })

C. res.status(200).json({ errors })

D. res.status(400).json({ errors: errors.map(e => ({ msg: e.message, param: e.field })) })

Solution

1. Step 1: Map errors to standard format with msg and param keys

   Express validation errors usually have 'msg' for message and 'param' for field name.

2. Step 2: Send response with status 400 and JSON containing errors array

   Use res.status(400).json(...) to send proper status and formatted errors.

3. Final Answer:

   res.status(400).json({ errors: errors.map(e => ({ msg: e.message, param: e.field })) }) -> Option D

4. Quick Check:

   Map errors to {msg, param} and send with 400 status [OK]

Hint: Map errors to {msg, param} and send with status 400 [OK]

Common Mistakes:

• Sending errors without mapping keys
• Using 200 status for errors
• Using wrong JSON key like errorMessages