You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the tested class contains fields of types that EqualsVerifier doesn't
know about (currently, it knows about the primitives, enum, String, and
Object), it can't instantiate them and they need to be supplied separately
using withPrefabValues.
It would be better if EqualsVerifier instantiates them automatically. This
is possible, since it can instantiate the tested class as well. It has to
instantiate all the fields recursively, until it hits a class that contains
only objects of known classes. (Maybe it can add instantiated objects to
the PREFAB_VALUES map as it goes along.)
Note: this will cause problems of the infinite loop variety with
(potentially) recursive data structures, such as graphs. It should be able
to detect this automatically, though.
Original issue reported on code.google.com by [email protected] on 16 Jul 2009 at 2:31
The text was updated successfully, but these errors were encountered:
Fixed!
withPrefabValues is now only necessary for recursive data structures, and maybe
one
or two weird corner cases that will hopefully get ironed out in the future :).
Original issue reported on code.google.com by
[email protected]
on 16 Jul 2009 at 2:31The text was updated successfully, but these errors were encountered: