Closed atreat closed 1 month ago
✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.
Package | Version | Score | Details |
---|
Warnings | |
---|---|
:warning: | No CHANGELOG entry added. |
:warning: | No tests added / modified. |
:warning: | **Sources/EmbraceCore/Capture/UX/Tap/TapCaptureService.swift#L137** - Returning Void in a function declaration is redundant (`redundant_void_return`) |
Generated by :no_entry_sign: Danger Swift against 98cc7065badc2623f6d7aced5a5cedb11bc52f4f
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 91.78%. Comparing base (
52375c4
) to head (ea2543a
). Report is 1 commits behind head on main.
Would this PR generate any breaking changes on the public API? If that's the case I'd:
a. Keep both old and new code (marking old as deprecated)
b. Specify this in someway.
I understand EmbraceSemantics
is meant to be exposed and used publicly.
These were incorrectly defined under
SpanType
. They are created/added to items that we record as SpanEvents.