Multiple validation errors are not populated correctly

[peaklabs-dev]

Inertia adapter(s) affected

• React
• Vue 3
• Svelte
• Not Applicable

JS package version

2.0.5

Backend stack (optional)

No response

Describe the problem

I'm not sure if I'm missing something but when there are multiple validation errors, Laravel should return an array of validation errors see https://laravel.com/docs/12.x/validation#validation-error-response-format. Currently, in the errors prop, there is always only one validation error the first one.

Steps to reproduce

Create a form in Svelte with a text input and the following rule: "username" => ["required", "alpha:ascii", "min:1", "max:3"]. Add a number, make it longer than three and see only the alpha rule error appear. Is this intended, or am I missing something? How can I show all validation errors each on a newline for example?

This is also true with vue.js:

Prop:

Instead of

username: [
    "The username field must only contain letters.",
    "The username field must not be greater than 3 characters"
]

[RobertBoes]

This is due to Inertia's Laravel adapter;

inertia-laravel/src/Middleware.php

Line 156 in a355007

return $errors[0];

Inertia has chosen to only share the first error message. If you don't want that behavior you can overwrite the resolveValidationErrors method in your own middleware

[peaklabs-dev]

@RobertBoes Thanks for sharing the place where this happens.

I still think this behavior is not right and should not be the default. Its just bad UX.

Submit, see 1 error, fix 1 error, submit, see the second error and then submit again.

[RobertBoes]

Well, Inertia has chosen that to be the default behavior and it has been since like forever. If you want different behavior, you can overwrite it and return all messages instead of the first one. Don't think this would ever change, or when it does it would need to be in a new major version, as it is quite a significant breaking change.

I'm not saying I disagree with you, because it's one things I change by default on any Inertia app. Just that Inertia has chosen for this approach, but I don't know why that was done.

[pascalbaljet]

Yes, this has been the default for a long time, maybe to match the behavior of the Blade @error directive.

It would be interesting to know if there are many users who change this behavior. We could perhaps introduce a Middleware::shareAllErrors() method for it.

[peaklabs-dev]

@pascalbaljet Could you give me some guidance on how you would like this to be implemented? I could create a PR if you'd like. I tried using a boolean prop in the share function called $shareAllErrors but it did not work very well. Also, it is not the cleanest approach.

[pascalbaljet]

Opened PR #784 for this.