Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

fix: look for 422 for invalid requests #278

Merged
merged 6 commits into from
May 9, 2019
Merged

fix: look for 422 for invalid requests #278

merged 6 commits into from
May 9, 2019

Conversation

XVincentX
Copy link
Contributor

@XVincentX XVincentX commented May 9, 2019 •
edited
Loading

This PR will make sure Prims will look for 422 responses in the document for invalid requests first; if not defined, Prism will generate one and not use the default response, if defined.

This replace the following behaviour: look for 400 response and if not defined, use the default response and, if not defined, then throw a 422

@XVincentX XVincentX merged commit 7a1c073 into develop May 9, 2019
@philsturgeon philsturgeon deleted the feat/422_first branch May 9, 2019 19:53
@XVincentX XVincentX mentioned this pull request May 23, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@philsturgeon philsturgeon philsturgeon approved these changes

@chris-miaskowski chris-miaskowski Awaiting requested review from chris-miaskowski

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@XVincentX @philsturgeon