Automatically share validation errors #135
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates this adapter to automatically share validation errors with Inertia.js, instead of making Laravel users do this manually, like this:
The key difference with the above method is that Inertia will automatically return only one error per field, instead of the Laravel default, which is an array of errors.
This is simpler, and honestly, I've literally never displayed multiple errors per field. This seems to be the consensus on Twitter as well.
That said, if folks prefer the other behaviour (multiple errors per field), all they need to do is manually share the validation errors like before (using the snippet above). This package's service provider will only share the validation errors if the
errorskey has not already been used. This behaviour also makes this a non-breaking change.The goal of this change is to make Inertia.js easier to setup in Laravel applications, and since sharing validation errors is so common, this seems worthwhile to bake into the adapter.