Thanks for the PR.
I think this has been rejected in the past (I'm not 100% sure though).
This can leak sensitive info to me, in case the cast is not planned.
Looks risky IMHO

@nicolas-grekas For the__toString() method i at least can think of situations where it can be executed accidentally when converting something to string (which is the same for other objects). But for thegetTraceAsString method it is not providing any other data that can be fetched by calling other methods of the class as well.

So i don't really see cases where this can leak sensitive data?

Fine for getTraceAsString. Do you have a use case where this would help?

As the FlattenException class should behave as much as possible like a php \Exception object Actually, that's never been a goal.

@fabpot if this is not the goal then at least the return type declaration ofSymfony\Component\HttpKernel\DataCollector\ExceptionDataCollector::getException is not correct, as this indicates to return a\Exception but at least when using this method from aWebTestCase it returns aSymfony\Component\Debug\Exception\FlattenException.

It the behaivor wanted is thatSymfony\Component\HttpKernel\DataCollector\ExceptionDataCollector::getException should return either\Exception orSymfony\Component\Debug\Exception\FlattenException then both should implement the same interface. The commit0208800 has changed the original behaivor.

@nicolas-grekas The use case i have mentioned is to access the exception of a failed request in aWebTestCase.

Any news here?

@fabpot have changed the method name to what@nicolas-grekas suggested. Tests have run through.

Thank you@Deltachaos.