Closed atreat closed 3 months ago
✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.
Package | Version | Score | Details |
---|
Warnings | |
---|---|
:warning: | No CHANGELOG entry added. |
Generated by :no_entry_sign: Danger Swift against 8197b80b480aa535462e81e5f11ec069665e7b63
Attention: Patch coverage is 94.52055%
with 4 lines
in your changes missing coverage. Please review.
Project coverage is 92.11%. Comparing base (
2ec8b91
) to head (8197b80
). Report is 8 commits behind head on main.
if somebody creates the span using the SpanBuilder (aka buildSpan public API), would they be able to use the end(errorCode:time:) w/o importing EmbraceOTelInternal or shall we suggest they set the status manually before ending?
I would not expect a caller to need to import EmbraceOTelInternal
. I'll make sure that is not required. We can also look into setting the status in the SpanProcessor instead to move this logic from the interface layer
I would not expect a caller to need to import EmbraceOTelInternal
This is necessary right now. Going to see what I can do to prevent this from being necessary
I would not expect a caller to need to import EmbraceOTelInternal
This is necessary right now. Going to see what I can do to prevent this from being necessary
It's good to know. If you see the solution would take longer, we can address it in another PR
Going to address the EmbraceOtelInternal
import requirement in another PR.
Updates recordCompletedSpan to use the
end(errorCode:time:)
method and properly setSpan.Status
Status will be
OK
iferrorCode
isnil
, otherwise it will beERROR
.Fixes duplication of
SpanErrorCode
andErrorCode
definitions