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 could add an option to carry the location of a span by generating a new Error() and forward that to the attributes, we could do it optionally by adding a new positional parameter that enable/disable generation. This would allow enhancing the stack print of errors with source location for the spans.
Additionally we could also expose a functionWithSpan API that allows a user to define a function that is automatically traced, something like:
We could add an option to carry the location of a span by generating a new Error() and forward that to the attributes, we could do it optionally by adding a new positional parameter that enable/disable generation. This would allow enhancing the stack print of errors with source location for the spans.
Additionally we could also expose a functionWithSpan API that allows a user to define a function that is automatically traced, something like:
cc @tim-smart
The text was updated successfully, but these errors were encountered: