Trace operator? #316
jessegrosjean
started this conversation in
Ideas
Replies: 2 comments 3 replies
-
It's making for nice debug traces:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes please, I would love to something like this in the lib. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is there any interest to add a trace operator? I have an implementation that's working pretty well. I'm wondering if I should clean it up and make a pull request.
I think it would be a good/better solution for these issues:
It works by adding a
.trace(label:)
operator. This operator returns upstream output, so you don't need to modify your model to make a trace. Instead trace data is stored in a thread local context. To make a trace and get the resulting context you will:The trace is stored as a list of events:
The context stores the successful path, plus it also stores all the failed paths.
Compared to the above solutions:
withRange
requires.Beta Was this translation helpful? Give feedback.
All reactions