Added support for __debugInfo() magic method.

[sallyx]

• bug fix? no
• new feature? yes
• BC break? yes

After this change result from \Tracy\Dumper::dump() will reflect the return value from __debugInfo() magic method (if defined).

As this might change output, I consider it as a BC break.

[JanTvrdik]

I'm strongly against using __debugInfo() by default because it hides the actual object state.

[JanTvrdik]

Also see #135, you can use

Tracy\Dumper::$objectExporters[NULL] = function ($obj) {
    return method_exists($obj, '__debugInfo') ? $obj->__debugInfo() : (array) $obj;
};

[sallyx]

Yes, but that's exactly what is __debugInfo() for :-)

I missed that PR. Anyway, thanks for the code example ;-)

[milo]

@sallyx I trust to my code, so I would accept __debugInfo() on my classes. But when I work with 3rd party code, I really want to see the real content of the object and not the trimmed one.

[sallyx]

Ok, I could add option [ Dumper::DEBUGINFO => FALSE ] like it was in #135 ...