Joi as validation alternative in Express - Step-by-Step Execution

Concept Flow - Joi as validation alternative

Receive HTTP Request

↓

Extract Data from Request

↓

Define Joi Schema

↓

Validate Data Against Schema

↓

Proceed

↓

Next Middleware

This flow shows how Joi validates incoming data in Express: data is checked against a schema, then either accepted or rejected with an error.

Execution Sample

Express

const schema = Joi.object({ name: Joi.string().required() });
const { error, value } = schema.validate(req.body);
if (error) return res.status(400).send(error.details[0].message);
next();

This code validates the request body to ensure 'name' is a required string, sending an error if validation fails.

Execution Table

Step	Action	Input Data	Validation Result	Next Step
1	Receive request	{ name: 'Alice' }	Not validated yet	Validate data
2	Validate data	{ name: 'Alice' }	Valid	Call next()
3	Middleware passes	N/A	N/A	Request proceeds
4	Receive request	{ name: 123 }	Not validated yet	Validate data
5	Validate data	{ name: 123 }	Invalid: name must be a string	Send 400 error
6	Send error response	N/A	Error sent	Stop processing

💡 Execution stops when validation fails and error response is sent, or proceeds if data is valid.

Variable Tracker

Variable	Start	After Step 2 (valid)	After Step 5 (invalid)
req.body	N/A	{ name: 'Alice' }	{ name: 123 }
error	undefined	undefined	{ details: [{ message: 'name must be a string' }] }
value	undefined	{ name: 'Alice' }	{ name: 123 }

Key Moments - 2 Insights

Why does validation fail when name is a number?

Because the Joi schema requires 'name' to be a string. The execution_table row 5 shows validation fails with message 'name must be a string'.

What happens if validation passes?

The middleware calls next() to continue processing, as shown in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution_table, what is the validation result at step 2?

A Not validated yet

B Invalid

C Valid

D Error sent

💡 Hint

Check the 'Validation Result' column at step 2 in execution_table.

At which step does the middleware send a 400 error response?

A Step 6

B Step 5

C Step 3

D Step 4

💡 Hint

Look for 'Send error response' action in execution_table.

If the schema required 'age' as a number, how would the variable 'error' change after validation?

A It would always contain an error

B It would be undefined if age is valid

C It would contain a string value

D It would be the validated value

💡 Hint

Refer to variable_tracker for 'error' variable changes after validation.

Concept Snapshot

Joi validates data by defining a schema.
Use schema.validate(data) to check input.
If error exists, send response with error message.
If valid, call next() to continue.
This helps keep data clean and safe.

Full Transcript

This visual execution shows how Joi works as a validation alternative in Express. When a request arrives, the data is extracted and checked against a Joi schema. If the data matches the schema, the middleware calls next() to continue processing. If the data is invalid, an error message is sent back with status 400, and processing stops. Variables like 'error' and 'value' track validation results. This method helps ensure only correct data moves forward in the app.

Practice

1. What is the main purpose of using Joi in an Express application?

easy

A. To serve static files like images and CSS

B. To handle routing between different pages

C. To connect to a database

D. To validate incoming data and ensure it meets expected rules

Solution

1. Step 1: Understand Joi's role

   Joi is a library designed to check if data matches certain rules before using it.

2. Step 2: Compare with other Express tasks

   Routing, database connection, and serving files are handled by other parts of Express or middleware, not Joi.

3. Final Answer:

   To validate incoming data and ensure it meets expected rules -> Option D

4. Quick Check:

   Joi validates data = A [OK]

Hint: Joi is all about checking data rules fast [OK]

Common Mistakes:

• Confusing Joi with routing or database tools
• Thinking Joi serves files
• Assuming Joi manages app navigation

2. Which of the following is the correct way to define a Joi schema for a required string named username?

easy

A. const schema = Joi.string().required();

B. const schema = Joi.required().string();

C. const schema = Joi.string.required();

D. const schema = Joi.string().isRequired();

Solution

1. Step 1: Recall Joi syntax for strings

   Joi.string() creates a string schema, and .required() marks it as mandatory.

2. Step 2: Check method chaining order

   The correct chaining is Joi.string().required(), not Joi.required().string() or others.

3. Final Answer:

   const schema = Joi.string().required(); -> Option A

4. Quick Check:

   Joi.string().required() syntax = B [OK]

Hint: Use Joi.string().required() to make a string mandatory [OK]

Common Mistakes:

• Placing .required() before .string()
• Using .isRequired() which is not a Joi method
• Missing parentheses after string()

3. Given this Joi schema and data:

const schema = Joi.object({ age: Joi.number().min(18).required() });
const data = { age: 16 };
const result = schema.validate(data);

What will result.error contain?

medium

A. Null because Joi does not check numbers

B. Null because age is valid

C. An error object because age is less than 18

D. An error object because age is missing

Solution

1. Step 1: Understand the schema rules

   The schema requires age to be a number, at least 18, and present.

2. Step 2: Check the data against rules

   Data has age = 16, which is less than the minimum 18, so validation fails.

3. Final Answer:

   An error object because age is less than 18 -> Option C

4. Quick Check:

   Age 16 < 18 causes error = D [OK]

Hint: Min 18 means below 18 triggers error [OK]

Common Mistakes:

• Thinking 16 passes min(18)
• Assuming missing age error instead
• Believing Joi ignores number checks

4. You wrote this code to validate an email:

const schema = Joi.object({ email: Joi.string().email() });
const data = { email: 12345 };
const result = schema.validate(data);

What is the main problem here?

medium

A. The email method is missing parentheses

B. The email field is not a string, so validation fails

C. Joi.string() cannot be used with email validation

D. The schema object is missing .required()

Solution

1. Step 1: Check data type for email

   Email expects a string, but data has a number (12345), which is invalid.

2. Step 2: Confirm Joi email method usage

   Joi.string().email() is correct syntax; parentheses are present.

3. Final Answer:

   The email field is not a string, so validation fails -> Option B

4. Quick Check:

   Email must be string, got number = A [OK]

Hint: Email must be string, numbers cause validation error [OK]

Common Mistakes:

• Ignoring data type mismatch
• Thinking .email() needs no parentheses
• Assuming .required() is always needed

5. You want to validate a user object with name (string, required), age (optional number, min 0), and email (required valid email). Which Joi schema correctly enforces these rules?

hard

A. Joi.object({ name: Joi.string().required(), age: Joi.number().min(0), email: Joi.string().email().required() })

B. Joi.object({ name: Joi.string(), age: Joi.number().min(0).required(), email: Joi.string().email() })

C. Joi.object({ name: Joi.string().required(), age: Joi.number().min(0).required(), email: Joi.string().email() })

D. Joi.object({ name: Joi.string(), age: Joi.number(), email: Joi.string().email().required() })

Solution

1. Step 1: Check required fields

   Name and email must be required, so .required() must be on both.

2. Step 2: Check optional age with min 0

   Age is optional, so no .required(), but min(0) applies.

3. Step 3: Validate each option

   Joi.object({ name: Joi.string().required(), age: Joi.number().min(0), email: Joi.string().email().required() }) matches all rules exactly; others miss required or optional correctly.

4. Final Answer:

   Joi.object({ name: Joi.string().required(), age: Joi.number().min(0), email: Joi.string().email().required() }) -> Option A

5. Quick Check:

   Required name/email, optional age min 0 = C [OK]

Hint: Required fields get .required(), optional just rules [OK]

Common Mistakes:

• Marking optional age as required
• Missing .required() on name or email
• Confusing order of chaining methods