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
There's no way to explicitly call the method of the wrapped object. It's the default behavior, but as soon as a call is configured, this behavior is lost and there's no way to restore it. For instance, if we do this:
Labelling as breaking because it will force an update to the interfaces that provide the fluent API. Optimistically putting in milestone vNext, because it's currently slated to be 6.0.0, and it would be nice to get our breaking changes in now.
Currently, when using a wrapping fake like this:
There's no way to explicitly call the method of the wrapped object. It's the default behavior, but as soon as a call is configured, this behavior is lost and there's no way to restore it. For instance, if we do this:
The
Bar
method will return a default value, instead of the value from the wrapped object.A possible workaround is to do something like this:
It's reasonably simple in this specific case, but if the method had arguments it would be much uglier.
A better alternative would be to introduce a new
CallsWrappedMethod
method:CallsWrappedMethod
would throw if the fake is not a wrapping fake, of course.The text was updated successfully, but these errors were encountered: