Check if response status is unprocessableEntity#31
Merged
marcelolx merged 2 commits intorails:mainfrom Aug 12, 2021
olimart:patch-1
Merged
Check if response status is unprocessableEntity#31marcelolx merged 2 commits intorails:mainfrom olimart:patch-1
marcelolx merged 2 commits intorails:mainfrom
olimart:patch-1
Conversation
Collaborator
|
Can you fix the linting issue? |
Contributor
Author
Done. I think you need to approve the run of CI. |
Collaborator
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR adds a convenient helper to check for
unprocessableEntityresponse status.I bet we don't want to add a helper for each status code but this is motivated by the fact that Rails now returns
422status code by default for form submission with error rails/rails#41026So, we can legitimately expect doing this kind of check more often.