Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ConstraintViolations context determines HTTP status #993
Due to #842, validation opens up new opportunities and by happenstance, a new bug. Now validations can be done on resource query parameters, return values, etc, and this, in my opinion is a good thing.
The pitfall I ran into is that the current
This pull request attempts to fix the current behavior, which will return 422 on return values and
There is an issue with this implementation: I'm uncomfortable that the only sane implementation for checking if constraint violation was fired on a parameter is by regex. Please advise.
EDIT: I found a better way than regex from the Jersey code