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
We currently have this which is I think a regression. Not the error itself, but rather the fact that it isn't reporting on the location of the .if, .each, or .chain call within the application, but rather still referring to the gem internals.
It would be better to have a source_location line within the application for each interactor and DSL method call that fires an interactor. run/run!/call/call!
running rspec without --backtrace
# ./app/interactors/point_of_failure.rb:12:in `call'
# ./somewhere/in/the/app/code.rb:9:in `block (2 levels) in <module:Somewhere::In::The::App::Code>'
where PointOfFailure is deeply nested call after Somewhere::In::The::App::Code.call!
I.e. instead of running rspec with --backtrace and seeing the following
We currently have this which is I think a regression. Not the error itself, but rather the fact that it isn't reporting on the location of the
.if
,.each
, or.chain
call within the application, but rather still referring to the gem internals.It would be better to have a source_location line within the application for each interactor and DSL method call that fires an interactor. run/run!/call/call!
running rspec without
--backtrace
where
PointOfFailure
is deeply nested call afterSomewhere::In::The::App::Code.call!
I.e. instead of running rspec with
--backtrace
and seeing the followingwe should see something more like (pseudocode) without
--backtrace
Then have a trace as above but with DSL internal interspersed in the stack trace.
The text was updated successfully, but these errors were encountered: