docs(nextjs-ssr): clarify need for HTML name attribute in form submissions #1574
Conversation
… submissions add inline comments to client components in next.js server action examples highlighting the need to explicitly set the name attribute on input fields for native POST submissions (e.g. with Next.js Server Actions). This avoids confusion where inputs may otherwise be omitted from formData. closes TanStack#1565
| @@ -293,7 +293,7 @@ export const ClientComp = () => { | |||
| return ( | |||
| <div> | |||
| <input | |||
| name="age" | |||
| name="age" // must explicitly set the name attribute for the POST request | |||
There was a problem hiding this comment.
Would it make sense to use name={field.name} instead of a new string? Or is there something users should know about what names to choose for the JSX elements?
There was a problem hiding this comment.
Yes, you're absolutely right (I feel like an AI assistant with that response 😄)!
Since we have access to the field object on the render prop, we should definitely use name={field.name} rather than hard-coding the name attribute. That's what I'm doing in my own project in the component that uses useFieldContext, but I forgot we have access to the field object here as well. Good catch!
There was a problem hiding this comment.
Sounds good, then! Could you check the whole file for the name prop? Once that's committed, I'll merge. The comment is fine for just the first instance of it imo.
add inline comments to client components in next.js server action examples highlighting the need to explicitly set the name attribute on input fields for native POST submissions (e.g. with Next.js Server Actions). This avoids confusion where inputs may otherwise be omitted from formData.
closes #1565