Dave Marshall

That class is a bit of a special one, in that it's used as the template to generate the doubles. In the most basic form: ``` php $classToMock = "Foo";...

@timothyfisherdev try ``` php $mock = Mockery::mock('overload:' . MyImplementation::class, MyInterface::class); ```

I don't think it's a bad idea, but it feels difficult to come up with a sensible name for the configuration value etc. I'm also less inclined to add mechanisms...

@robertbasic what do you think? As said, I'm not against it, but it's not something I'd ever use. I use `byDefault` and the quick definitions to setup sane defaults, usually...

Hi Leroy, I believe someone is drafting a PR to help with that right now, #1000, so if you would like to review that, that would be a great help.

It's a strange one, the only reason we have the `LegacyMockInterface` is to support mocking classes that have `allows` and `expects` methods, which clash with the `MockInterface`'s methods of the...

How about we say we're definitely dropping it for 2.0. If we get to a stage where the HHVM code is holding us back, maybe we talk about ripping it...

Thank you for the PR. I'll try and look in to the test runs.

The more I think about this, the less and less enamoured I am by it. I've been using Mockery extensively for almost 10 years and never have I really thought...

👍👍 On Sun, 7 Jun 2020, 20:39 Graham Campbell, wrote: > I propose to deprecate getWhiteListedMethods and replace with > getAllowedMethods, and similarly for blacklist and associated variable > names....