[Mistakes]: Server Functions examples use incompatible action signatures

Summary

The updateName Server Function is defined as updateName(name), but the page later uses it as a direct form action and with useActionState. These usages pass different arguments, so the examples cannot work with the shown function.

Page

https://react.dev/reference/rsc/server-functions

Details

The page defines:

export async function updateName(name) {
  if (!name) {
    return {error: 'Name is required'};
  }
  await db.users.updateName(name);
}

There are several inconsistencies/mistakes:

• In “Server Functions with Actions”, the input does not update the name state, so updateName(name) always receives ''.

• On success, updateName returns undefined, but the client destructures {error} from its result.

• When passed to <form action={updateName}>, React calls updateName with FormData, not a string.

• When passed to useActionState, React calls it with (previousState, FormData), and it must consistently return the next state.

The examples should define a Server Function with the correct parameters and return value for each usage.

Comece pela página de referência de Server Functions em https://react.dev/reference/rsc/server-functions e compare o exemplo updateName entre “Server Functions with Actions”, a ação direta de formulário e o uso de useActionState. Considera-se concluído quando os parâmetros e o valor de retorno de cada exemplo correspondem à forma como o React o invoca, incluindo os argumentos FormData e de estado anterior.