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
As discovered in #214, withPrefabValues can generate illegal reflective access warnings if used on a type that is defined in a different module that isn't open for reflection. This happens when EqualsVerifier tries to clone the red value into the redCopy value.
This should be fixed. If that's not possible, there should be a workaround (for instance, by adding an overloaded withPrefabValues method with a redCopy parameter.
The text was updated successfully, but these errors were encountered:
It's fixed in version 3.1. You'll still get the illegal reflective access warnings if you run without --illegal-access=deny, which is unfortunate, but there will be no InaccessibleObjectException when you run with it.
As discovered in #214,
withPrefabValues
can generate illegal reflective access warnings if used on a type that is defined in a different module that isn't open for reflection. This happens when EqualsVerifier tries to clone thered
value into theredCopy
value.This should be fixed. If that's not possible, there should be a workaround (for instance, by adding an overloaded
withPrefabValues
method with aredCopy
parameter.The text was updated successfully, but these errors were encountered: