The <Form> component in Inertia does not provide strong type safety by itself

[ramosramosramos]

Problem

Currently, the <Form> component in Inertia is great for quick usage, but it lacks TypeScript type safety.
All form fields are treated as untyped strings, which leads to:

• Typos in field names not being caught at compile time
• No autocomplete for form fields
• No way to enforce a strict form data structure

Example (current behavior)

<Form method="post" action="/users">
  <input name="emial" /> {/* typo, but no TypeScript error */}
</Form>

---

Proposed Solution

Allow the <Form> component to accept a generic type for its data shape, similar to how useForm<T>() works.

Example (proposed)

type UserForm = {
  email: string
  password: string
}

<Form<UserForm> method="post" action="/users">
  <input name="email" />     {/*  autocomplete */}
  <input name="password" />  {/*  type checked */}
  <input name="emial" />     {/*  TypeScript error */}
</Form>

---

Benefits

• Prevents bugs caused by typos in field names
• Provides better autocomplete and developer experience in TypeScript projects
• Aligns <Form> with the type-safety already available in useForm<T>()
• No impact on developers who aren’t using TypeScript

---

[pascalbaljet]

We're exploring this and working on it :)