We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in /node_modules/@inertiajs/react/types/useForm.d.ts we can see that : errors: Partial<Record<keyof TForm, string>>
errors: Partial<Record<keyof TForm, string>>
But in the docs, we have this usage : redirect_to new_user_url, inertia: { errors: user.errors }
redirect_to new_user_url, inertia: { errors: user.errors }
which actually create errors with type Partial<Record<keyof TForm, string[]>> instead.
Partial<Record<keyof TForm, string[]>>
Should we do something about it ?
The text was updated successfully, but these errors were encountered:
Maybe in Laravel it is a string?
string
Anyways, I added this patch for now
diff --git a/node_modules/@inertiajs/react/types/useForm.d.ts b/node_modules/@inertiajs/react/types/useForm.d.ts index de427dc..7cee9a6 100644 --- a/node_modules/@inertiajs/react/types/useForm.d.ts +++ b/node_modules/@inertiajs/react/types/useForm.d.ts @@ -7,7 +7,7 @@ type FormOptions = Omit<VisitOptions, 'data'>; export interface InertiaFormProps<TForm extends FormDataType> { data: TForm; isDirty: boolean; - errors: Partial<Record<keyof TForm, string>>; + errors: Partial<Record<keyof TForm, string[]>>; hasErrors: boolean; processing: boolean; progress: Progress | null;
Sorry, something went wrong.
No branches or pull requests
in /node_modules/@inertiajs/react/types/useForm.d.ts we can see that :
errors: Partial<Record<keyof TForm, string>>
But in the docs, we have this usage :
redirect_to new_user_url, inertia: { errors: user.errors }
which actually create errors with type
Partial<Record<keyof TForm, string[]>>
instead.Should we do something about it ?
The text was updated successfully, but these errors were encountered: