Custom object formatters

[MartinMystikJonas]

Possibility to set custom objet formatters for specific classes or interfaces. If formatter is set it's used instead of default formatter outputing public properties.

        \Mockery::getConfiguration()->setObjectFormatter(
            'ClassWithCustomFormatter',
            function($object) {
                return array(
                    "properties" => array(
                        "stringProperty" => $object->stringProperty
                    ),
                    "getters" => array(
                        "gettedProperty" => $object->getArrayProperty()
                    )
                );
            }
        );

[davedevelopment]

Looks great!

[robertbasic]

@MartinMystikJonas hey, thanks for the PR! Can you fix the conflicts and update the PR based on @davedevelopment's and mine requests? Thank you!

[MartinMystikJonas]

Finally had time to finish this. Sorry about three years gap but after our daughter was born I had only little time for open source :-)

[MartinMystikJonas]

Let me know if you want to merge it I will squash commits

[MichaelKubovic]

Friendly ping, is there anything we can do to merge this?

[GrahamCampbell]

why?

[MartinMystikJonas]

It is often useful to be able to compare object identities not only their class + some optional custom info from formatter. Should I remove it?

[GrahamCampbell]

I mean why the md5. Just use spl_object_id.

[MartinMystikJonas]

Besause spl_object_id is hard to compare visually becaue usually two instances have most characters of spl_object_hash identical. Using of md5 of spl_object_hash is quite common practice i saw in many libraries.

[MartinMystikJonas]

For example I just used it on two objects and I got:
000000002f73941b000000004f808351 and 000000002ffa4e380000000026e9a821
If you use md5 it becomes different at the first sight:
69850868ab17d5cd4d7effccd55ba63c and 43147e68957af1fcbd045979c3c3fda3