0Pricing
Next.js 15 Fullstack (App Router + Server Actions) · 课时

使用 useActionState 处理字段级验证错误

从操作中返回结构化验证结果,并以内联方式渲染每个字段的错误消息。

使用 useActionState 处理字段级验证错误 是 CoddyKit 上的免费 Next.js 15 Fullstack (App Router + Server Actions) 课时。 这是第 3 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Next.js 15 Fullstack (App Router + Server Actions) 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

Why Field-Level Errors?

When a form fails validation, users need to know exactly which field is wrong and why. A single banner saying "Something went wrong" forces them to guess.

In Next.js 15, Server Actions paired with useActionState let you return a structured result from the server and render an inline error right beneath each input.

  • email is invalid → show the error under the email field
  • password is too short → show it under the password field

This lesson shows how to return that structure and render it cleanly.

Shaping the Action State

Start by deciding the shape of what your action returns. A good pattern keeps per-field errors in an errors map keyed by field name, where each value is an array of messages.

Defining a TypeScript type makes the contract explicit for both the action and the component.

export type FieldErrors = {
  email?: string[];
  password?: string[];
};

export type SignupState = {
  errors?: FieldErrors;
  // value the user typed, so we can re-fill the form
  values?: { email?: string };
  // a top-level message for non-field errors
  message?: string;
};

export const initialState: SignupState = {};

Validating with Zod in the Action

A schema library like Zod gives you both validation and a ready-made error structure. Call safeParse so failures don't throw — instead you inspect the result.

flatten().fieldErrors returns exactly the { field: string[] } shape we designed, so it maps directly onto our state.

import { z } from 'zod';

const SignupSchema = z.object({
  email: z.string().email('Enter a valid email'),
  password: z.string().min(8, 'At least 8 characters'),
});

const result = SignupSchema.safeParse({
  email: 'not-an-email',
  password: '123',
});

if (!result.success) {
  // { email: ['Enter a valid email'], password: ['At least 8 characters'] }
  console.log(result.error.flatten().fieldErrors);
}

The Server Action Signature

An action used with useActionState receives two arguments: the previous state and the submitted FormData. It must return the next state.

Mark the file or function with 'use server'. Read values with formData.get(...), validate, and return errors instead of throwing.

'use server';

import { z } from 'zod';
import type { SignupState } from './state';

const SignupSchema = z.object({
  email: z.string().email('Enter a valid email'),
  password: z.string().min(8, 'At least 8 characters'),
});

export async function signup(
  prevState: SignupState,
  formData: FormData,
): Promise<SignupState> {
  const email = String(formData.get('email') ?? '');
  const password = String(formData.get('password') ?? '');

  const parsed = SignupSchema.safeParse({ email, password });

  if (!parsed.success) {
    return {
      errors: parsed.error.flatten().fieldErrors,
      values: { email }, // keep email, never echo the password
    };
  }

  // ...persist the user here...
  return { message: 'Account created' };
}

Wiring useActionState

In your client component, call useActionState(action, initialState). It returns a tuple:

  • state — the latest value your action returned
  • formAction — pass this to the form's action prop
  • isPending — true while the action runs (great for disabling the button)

Remember the 'use client' directive — hooks only run in client components.

'use client';

import { useActionState } from 'react';
import { signup } from './actions';
import { initialState } from './state';

export function SignupForm() {
  const [state, formAction, isPending] = useActionState(
    signup,
    initialState,
  );

  return (
    <form action={formAction}>
      {/* inputs go here */}
      <button disabled={isPending}>
        {isPending ? 'Creating...' : 'Sign up'}
      </button>
    </form>
  );
}

Rendering an Inline Error

To show a field error, read it from state.errors?.fieldName. Because each field holds a string array, render the first message (or map over all of them).

Use optional chaining so the very first render — when errors is undefined — doesn't crash.

<div>
  <label htmlFor="email">Email</label>
  <input
    id="email"
    name="email"
    type="email"
    defaultValue={state.values?.email}
  />
  {state.errors?.email && (
    <p className="error">{state.errors.email[0]}</p>
  )}
</div>

Accessibility: Linking Errors to Inputs

Screen readers should announce the error and tie it to the field. Two attributes do the heavy lifting:

  • aria-invalid — set true when the field has an error
  • aria-describedby — point to the id of the error element

Give the error element a stable id and a polite live region so updates are read aloud.

<input
  id="email"
  name="email"
  type="email"
  defaultValue={state.values?.email}
  aria-invalid={!!state.errors?.email}
  aria-describedby="email-error"
/>
{state.errors?.email && (
  <p id="email-error" className="error" aria-live="polite">
    {state.errors.email[0]}
  </p>
)}

Preserving User Input

Because the form re-renders from server state, an uncontrolled input would lose what the user typed. Return the safe values from the action and feed them back with defaultValue.

Never echo passwords back to the client. Only return non-sensitive fields like email so the user doesn't retype everything after a validation error.

// in the action, on failure:
return {
  errors: parsed.error.flatten().fieldErrors,
  values: { email }, // safe to round-trip
  // password is intentionally omitted
};

// in the component:
<input name="email" defaultValue={state.values?.email} />
<input name="password" type="password" /> {/* always blank */}

A Pure Validation Helper You Can Test

Validation logic doesn't need Next.js to be correct. Extract it into a pure function that takes plain values and returns the same { field: string[] } error map. This is trivially unit-testable and runnable on any judge.

type FieldErrors = { email?: string[]; password?: string[] };

function validateSignup(email: string, password: string): FieldErrors {
  const errors: FieldErrors = {};

  const emailOk = /^[^@\s]+@[^@\s]+\.[^@\s]+$/.test(email);
  if (!emailOk) errors.email = ['Enter a valid email'];

  if (password.length < 8) errors.password = ['At least 8 characters'];

  return errors;
}

const e1 = validateSignup('bad', '123');
console.log(e1); // { email: [...], password: [...] }

const e2 = validateSignup('a@b.co', 'longenough');
console.log(Object.keys(e2).length === 0); // true

console.log(JSON.stringify(validateSignup('x@y.com', 'short')));

Multiple Errors per Field

A single field can fail several rules at once (empty, too short, wrong format). Since each entry is an array, you can render every message as a list.

Zod naturally accumulates multiple issues per field, so fieldErrors.password may contain more than one string.

{state.errors?.password && (
  <ul className="error-list">
    {state.errors.password.map((msg) => (
      <li key={msg}>{msg}</li>
    ))}
  </ul>
)}

Top-Level vs Field Errors

Not every failure belongs to a field. A duplicate-email conflict from the database, or a generic server fault, is a form-level message.

Keep both channels in your state: errors for per-field issues and message for the whole form. Render the top-level message above the fields so it isn't missed.

// in the action, after a successful parse:
try {
  await createUser(email, password);
} catch (err) {
  if (isUniqueViolation(err)) {
    return { errors: { email: ['Email already in use'] } };
  }
  return { message: 'Something went wrong. Please try again.' };
}

// in the component, above the fields:
{state.message && <p role="alert">{state.message}</p>}

Quick Check

Test your understanding of the action contract used by useActionState.

Recap

You can now build field-level validation with Server Actions and useActionState:

  • Shape the state with an errors map of { field: string[] }, plus optional values and a top-level message.
  • Validate in the action with safeParse and return flatten().fieldErrors — return, never throw.
  • Wire the hook with useActionState(action, initialState) and pass formAction to the form; use isPending for the button.
  • Render inline from state.errors?.field, with aria-invalid and aria-describedby for accessibility.
  • Preserve input via defaultValue, but never echo passwords.
  • Separate channels: per-field errors vs form-wide message.

常见问题解答

「使用 useActionState 处理字段级验证错误」课时是免费的吗?

是的 — 「使用 useActionState 处理字段级验证错误」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Next.js 15 Fullstack (App Router + Server Actions) 课程的其余内容,请升级到 CoddyKit PRO。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 4 节课。

「使用 useActionState 处理字段级验证错误」这节课中我会学到什么?

从操作中返回结构化验证结果,并以内联方式渲染每个字段的错误消息。 你通过在浏览器中直接运行的动手代码来练习 Next.js 15 Fullstack (App Router + Server Actions),全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Next.js 15 Fullstack (App Router + Server Actions) 需要有经验吗?

无需任何先前经验。CoddyKit 上的 Next.js 15 Fullstack (App Router + Server Actions) 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 3 节课,共 4 节。

「使用 useActionState 处理字段级验证错误」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 Next.js 15 Fullstack (App Router + Server Actions) 课中编写并运行代码吗?

能。每节 Next.js 15 Fullstack (App Router + Server Actions) 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 使用表单 Action 属性实现渐进式增强
  2. 使用 useFormStatus 处理待提交与加载状态
  3. 使用 useActionState 处理字段级验证错误
  4. 使用 useOptimistic 提供即时反馈
← 返回 Next.js 15 Fullstack (App Router + Server Actions)