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
Image if errors happened, there's no good way to tell where exactly the location the error happened in the first place. Especially when each sub-interactions also have its composed interactions. Basically the backtrace from the top-level interaction to the first scene of the errors will be swallowed.
It'd good if
the errors remember the __FILE__ and __LINE__ of where errors.add happens
when merging errors from the composed sub-interaction, it should retain the file location info in the errors
probably the best place to save such info is in detailed_messages?
The text was updated successfully, but these errors were encountered:
I didn't look into the source yet. It depends on when does the exception being raised.
If the failed sub-interaction first return back to the top-level interaction and raise afterward, then the sub-interaction should wrap its caller information way up to the top-level.
If the failed sub-interaction raises in place, the compose method should simply set the backtrace from the error it captured.
Image if errors happened, there's no good way to tell where exactly the location the error happened in the first place. Especially when each sub-interactions also have its composed interactions. Basically the backtrace from the top-level interaction to the first scene of the errors will be swallowed.
It'd good if
__FILE__
and__LINE__
of whereerrors.add
happensdetailed_messages
?The text was updated successfully, but these errors were encountered: