Johan Blumenberg
Johan Blumenberg
We have been in contact with the google support, but after 3 months the only sensible response that we have gotten so far is that it might be related to...
We have created a patch to remove the background process, and this seems to solve the problem. We have used the same patch both in our Cloud Run services and...
As I wrote, this is just a proposal. There are probably better ways to solve the problem. > So to be clear, it doesn't look like you've removed the background...
@NagRock I added an exception if calling `imock()` with no `Proxy` support
@Markus-Ende Yes, only stubbing methods. That's why I made a separate function, `imock()`, because it works slightly different. But it's still quite useful to be able to automatically mock interfaces,...
@NagRock Is there anything blocking this PR?
Fixed a problem when retuning mock instances in `thenResolve()`: ``` when(mockedFoo.sampleMethodReturningObjectPromise(sampleValue)).thenResolve(instance(expectedResult)); ``` The problem is that the `Promise.resolve()` call will check if the given value is a promise, by checking...
Added support for mocking both properties or methods on interfaces. This will make all properties on the object to be stubbed as properties: ``` let mock: Foo = imock(MockPropertyPolicy.StubAsProperty); when(mock.foo).thenReturn('xyz');...
Added support for mocking interfaces containing both properties and methods. The default policy in the previous commit decides what happens with unknown properties. The type of a property can be...