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
hibernate validator: Remember annotated interface methods #5308
Conversation
Set<String> methodSet = inheritedAnnotationsToBeValidated.get(clazz.name()); | ||
if (methodSet == null) { | ||
methodSet = new HashSet<String>(); | ||
inheritedAnnotationsToBeValidated.put(clazz.name(), methodSet); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could collapse this down a bit using computeIfAbsent()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it isn't a concurrent set.. and my brain only remembered them there.
I'm away for a few days. I'll have a look when I'll get back. |
I'll also give it a look over the weekend but I'll leave the final approval to @gsmet since he's the sme on this |
Nice job! I do see however that the original issue mentions inherited methods from classes as well as interfaces and unless I misunderstood the changes, the class case is not handled? |
I will double check. I'll have to add an additional test, I think. I stuck with the testcase provided by @isikemre, which focused on interfaces. |
Cool, thanks! |
it looks it introduces issues in other PR (CI builds), I'm going to revert it, and @gsmet will have another look |
|
So there is flaky test |
Question: Did the test only fail in native mode? |
The one I saw was in native. |
resolves #1888
This includes #1913