Tom Chapman

I thought I'd tried that before. Went to my recipes, and there the any.do plugin was, in the top level `recipes` folder, not the `recipes/dev` folder. So I upgraded back...

@robertbasic unfortunately that isn't the case. The code originally provided, aside from including mockery, was all I ran to produce that output. These were both stand alone test scripts so...

@robertbasic Mockery isn't trying to overload `TestInterface` here. The second parameter is a list of interfaces the generated class should implement. At-least that's how it works according to both the...

@robertbasic Unfortunately both `alias:` and `overload:` are unaware of the interfaces implemented by the existing class. To discover this via reflection (which Mockery seems to use) they would have to...

@robertbasic I decided to show this in an example. This is obviously a _**very**_ crude example, but I'd expect a not overly un-expected extension of the the reason `overload:` was...

The issue with `overload:` is stemming from the appending of a `__construct` method in `Mockery\Generator\StringManipulation\Pass\InstanceMockPass` thanks to `$config->isInstanceMock()` returning `true`. This value defaults to `false` in the `Mockery\Generator\MockConfiguration` class and...

The above will solve the issue in a normal overloading situation, this specific issue is around overriding the `__construct` method

This has moved now to: http://www.aukweb.net/results/aaa/aaaclmb/ http://www.aukweb.net/results/aaa/aaavnts/aaaqual/