Closed mobasherswl closed 4 years ago
Bean verification checks that a call to Foo setter results in a change visible from Foo getter:
setFoo(xyz)
xyz.equals(getFoo())
It does not check if a call to Foo setter might result in a change to another property:
setFoo(xyz)
!xyz.equals(getBar()) ??
It's easy to see though why users might want the library to detect such likely unintended behavior. An improvement will be made to the library to detect it.
Thanks for reporting.
With 3.0.0-m6 release, such a bean should be detected.
Please give that a try.
Gitter chat was also created as another venue for asking questions.
The example class is given below. See setName method, where the value passed is set to both class members. The unit test passes without any error. Am I missing something?
`public class User { private String name; private String title;
}`