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
I would rather prefer to see it as has<FieldName>Satisfying(Consumer/Condition) pair of methods. Just like hasValueSatisfying for Optional or satisfies for list elements or other similar asserts. This way you can continue to fluently verify other complex fields of objectA. With getB()/withObjectB() approach you have no way to fluently return back to objectA assertions.
Enhancement
Use case:
I already do that manually, but I think it could be useful to be able to add this behavior automatically.
What do you think?
The text was updated successfully, but these errors were encountered: