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
@must could you elaborate? as per my understanding you can do it now manually. do you mean all calls in a call-stack should be automatically watched? like the whole call-tree should be watched and recorded by default?
What I initially meant was that it would be nice to be able to watch multiple independent calls in a row. For example, if I had an end point that is iteratively called multiple times, I would like to be able to see what happens in each call, that would enable me to debug when the problem happens in one of the several iterative calls. Otherwise, with the current tools available, I am only able to see the first call.
Also, yeah, because you just mention it right now, it would also be nice to be able to watch what happens inside all the called (internal/public connect) nodes (this would also solve the first point).
As the title says, it would be nice to have multiple calls in a row watched and listed with the developer being able to access each and play it back.
The text was updated successfully, but these errors were encountered: