Use validation rule, expect 422 for validation failure #2
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.
Use the default Laravel rule validation for internal consistency as outlined by @indykoning in the initial PR.
I'm still unsure whether or not we want to have the core throw a more specific error (like a
ValidationError
instead of aFetchError
) when it's a 422 so that we can catch that instead and not have to check the magic number 422, I personally think it would make this type of code nicer.