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
Is your feature request related to a problem? Please describe.
On a scenario where we have a mocked instance with methods that receive type arguments, proceedings like verify never take notice of type arguments,
// real calls
stub.someMethodWithTypeArgs<SomeType>()
stub.someMethodWithTypeArgs<SomeAnotherType>()
// verify callfinal result =verify(() => stub.someMethodWithTypeArgs<SomeType>());
print(result.callCount); // will be 2, even though we are verifying inly for calls passing `SomeType`.
Describe the solution you'd like
Take type arguments into consideration as much as positional and named arguments.
Describe alternatives you've considered
We could evolve to have Type Matchers like Any but probably not for the current state of the support of type arguments on dart.
verify(() => stub.someMethodWithTypeArgs<Any>());
Additional context
The fix would be probably be added here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
On a scenario where we have a mocked instance with methods that receive type arguments, proceedings like
verify
never take notice of type arguments,Describe the solution you'd like
Take type arguments into consideration as much as positional and named arguments.
Describe alternatives you've considered
We could evolve to have Type Matchers like
Any
but probably not for the current state of the support of type arguments on dart.Additional context
The fix would be probably be added here.
The text was updated successfully, but these errors were encountered: