Form Validation — Complete Guide
Form Validation — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of Next.js Tutorial on Toolliyo Academy.
On this page
Next.js Tutorial (LearnHub) · Lesson 19 of 100
Form Validation
Beginner → Intermediate → Advanced → Professional
Beginner · 1 — Foundations · ~12 min read · Module 2: Layouts & Styling
Introduction
This lesson is part of the beginner section. We explain Form Validation slowly, with examples you can copy and run. If something is unclear, read it twice — that is how everyone learns. Validation checks user input before save — required fields, email format, password strength. Do it on the server always; add client hints for faster feedback. Bad enrollment data corrupts LearnHub dashboards. Attackers bypass client-only checks — server validation is mandatory.
Form Validation appears in almost every LearnHub page you will build. Once it clicks, data fetching and auth become much easier.
When will you use this?
You use layouts and styling in every page you build from your first screen to production.
- Course catalogs, lesson sidebars, and instructor dashboards all use layouts and shared navigation.
- When a student opens a lesson page, nested layouts keep the header and progress bar consistent.
Real-world: Freshdesk-style support portal
The Customer support team building Freshdesk-style support portal uses Form Validation to reject empty emails and weak passwords before saving to the database. support agents never see the TypeScript files — they just get a fast, reliable ticket queue and reply interface.
Production-style code
'use server';
import { z } from 'zod';
const enrollSchema = z.object({
courseId: z.string().min(1),
email: z.string().email()
});
export async function enrollWithEmail(formData: FormData) {
const parsed = enrollSchema.safeParse({
courseId: formData.get('courseId'),
email: formData.get('email')
});
if (!parsed.success) {
return { errors: parsed.error.flatten().fieldErrors };
}
// save enrollment...
return { success: true };
}What happens in production: In Freshdesk-style support portal, getting Form Validation right means support agents trust the ticket queue and reply interface every day.
Lesson example (start here)
Copy this smaller example first. Once it works, compare it with the real-world code above.
'use server';
import { z } from 'zod';
const enrollSchema = z.object({
courseId: z.string().min(1),
email: z.string().email()
});
export async function enrollWithEmail(formData: FormData) {
const parsed = enrollSchema.safeParse({
courseId: formData.get('courseId'),
email: formData.get('email')
});
if (!parsed.success) {
return { errors: parsed.error.flatten().fieldErrors };
}
// save enrollment...
return { success: true };
}Line-by-line walkthrough
| Code | What it means |
|---|---|
'use server'; | Server Actions directive — function runs only on the server. |
import { z } from 'zod'; | Imports a module so you can use its exports in this file. |
const enrollSchema = z.object({ | Part of the Form Validation example — read it together with the lines before and after. |
courseId: z.string().min(1), | Part of the Form Validation example — read it together with the lines before and after. |
email: z.string().email() | Part of the Form Validation example — read it together with the lines before and after. |
}); | Closes a block started by { above. |
export async function enrollWithEmail(formData: FormData) { | Exported async function — often a Server Action or API handler. |
const parsed = enrollSchema.safeParse({ | Part of the Form Validation example — read it together with the lines before and after. |
courseId: formData.get('courseId'), | Part of the Form Validation example — read it together with the lines before and after. |
email: formData.get('email') | Part of the Form Validation example — read it together with the lines before and after. |
}); | Closes a block started by { above. |
if (!parsed.success) { | Part of the Form Validation example — read it together with the lines before and after. |
return { errors: parsed.error.flatten().fieldErrors }; | Part of the Form Validation example — read it together with the lines before and after. |
} | Closes a block started by { above. |
How it works (big picture)
- Zod schema defines rules.
- safeParse returns errors without throwing.
- Return field errors to the form for display.
Do this on your computer
- npm install zod
- Add schema to a Server Action
- Submit empty form — see errors returned
- Show errors in UI with useFormState
- Read the real-world section and name which part of LearnHub uses this topic.
- Run the example locally with npm run dev and confirm the same behavior.
- Change one value in the example (route, text, or course id) and predict what will happen before you save.
Experiments — try changing this
- Change a string or route in the example and save — watch the browser update.
- Break the code on purpose (remove a bracket), read the error overlay, then fix it.
- Change the API URL or course id and see how the page data changes.
Remember
Validate on the server always. Zod is a popular TypeScript choice. Return errors to the form for UX.
Common questions
Zod vs Yup?
Both work; Zod has excellent TypeScript inference.
How long should I spend on Form Validation?
Until you can explain it in your own words and run the example without looking at the answer. Beginners often need 30–60 minutes per new concept; setup lessons may take one afternoon.
What if I get stuck on Form Validation?
Re-read the line-by-line walkthrough, check the terminal and browser overlay for errors, and compare your code character-by-character with the example. Search the exact error text — someone else had it too.
Where is Form Validation used in real jobs?
See the real-world section above — the same pattern appears in LMS, e-commerce, SaaS, and dashboards. Interviewers ask you to explain it using one concrete example.