Mattia Tommasone
Mattia Tommasone
Thanks for looking into this! The non-inlined overloads look good to me. Feel free to finish the PR and I'll be super glad to review it :)
Just released 1.13.5!
Re: the failing tests: I think you can rewrite them both as `verify(exactly = 0)` as @jcopenhop suggested.
That seems like a bug with `anyConstructed`. I think we can just skip the test for now and temporarily accept that `anyConstructed` is not working with `exactly` at the moment....
While I think @abcarrell's reasoning is correct and mocking interfaces is generally not a good idea, I understand the need to fix this issue: perhaps looking into the changes that...
I think there are still a few open points to be addressed before this can be merged.
This is a very interesting finding, thanks for taking the time to investigate this! I agree `unmockkAll` should also dispose of existing stubs, it really seems like a bug to...
I don't think mocking companion objects is a good idea. What is the behavior you are trying to achieve here, exactly?
`init` blocks cannot be mocked. Out of curiosity, why is your `fetchAllApis()` call in an `init` block rather than in a constructor?
@RyanThomas73, 2 days ago we had an internal, widespread issue that caused increased latency on the whole API, not just the .NET client library, so that was likely the reason...