-
Notifications
You must be signed in to change notification settings - Fork 30
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.
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
No need to validate values for JsonNullable.undefined() #12
Comments
Thanks for reporting. Would you do the fix ? |
Hi, sure. But I'm not able to create branch in this repository.
|
@VictorKrapivin to submit a PR, you need to fork the repo, create a branch in the fork, then you can PR with the help of GitHub. See details here. |
…defined Issue #12 - No need to validate values for JsonNullable.undefined()
Closed by #13 |
@cbornet Any plans for release? |
@cbornet Hi! Is it possible to release this fix in 0.2.1? |
If I remember well, I have published the last release to maven central. I am waiting for feedback, just to be sure. |
Version 0.2.1 was released! |
@jmini Thanks!! |
At the moment value initialized as undefined() is treated as null within validation.
Following code demonstrates issue:
Here violations should be empty, because JSR380 constraints address value within JsonNullable container, not container itself. So testObject is valid. But actual behavior gives violations.
The text was updated successfully, but these errors were encountered: