Closed zachdaniel closed 5 years ago
I've settled on accepting that some calls silently ignore errors, and have illustrated that behavior in tests and in documentation.
Totals | |
---|---|
Change from base Build 971d501c-6d07-4be5-bc75-90c95cf7afb9: | 0.9% |
Covered Lines: | 211 |
Relevant Lines: | 253 |
This addresses some but not all of the issues in #65. I'm still not sure how we should return from
start_trace
start_span
finish_trace
finish_span
and thecontinue_*
functions if given invalid updates. Its been discussed in slack, and we probably shouldn't just skip starting the span, and we also should raise an error. Likewise, returning{:error, error}
but still starting the trace/span might be wrong. Really not sure of the best path forward there.