You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if an exception is thrown inside the handler without defining either message or code arguments, and explicetely only using previous, the messenger:failed:show command shows an output containing an exception like so:
Now debugging this message has become quite a bit harder, as nothing is shown regarding the previous exception (not even the previous message or code).
Ofcourse! But could you tell me which branch I need to target? I was under the assumption to target 6.4 because it is stated in the contribution docs to target 6.4 (which is the previous minor version), but the PR template tells me to target 7.1 for features. So that's somewhat confusing.
Description
Problem
Currently if an exception is thrown inside the handler without defining either
message
orcode
arguments, and explicetely only usingprevious
, themessenger:failed:show
command shows an output containing an exception like so:messenger:failed:show 118 -vvv
Now debugging this message has become quite a bit harder, as nothing is shown regarding the previous exception (not even the previous message or code).
Possible solution
Add
Caster::PREFIX_VIRTUAL.'previous' => $flattenException->getPrevious(),
atAbstractFailedMessagesCommand#L190
.Example
App\Message\TestLoggerMessage
App\MessageHandler\TestLoggerMessageHandler
The text was updated successfully, but these errors were encountered: