-
Notifications
You must be signed in to change notification settings - Fork 929
feat(sdk-logs)!: Changed LogRecord
to be an interface
#5749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(sdk-logs)!: Changed LogRecord
to be an interface
#5749
Conversation
LogRecord
to be an interface
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5749 +/- ##
=======================================
Coverage 95.01% 95.01%
=======================================
Files 303 303
Lines 7957 7957
Branches 1610 1610
=======================================
Hits 7560 7560
Misses 397 397
🚀 New features to boost your workflow:
|
c875d5b
to
c8bc527
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks, good - but this is breaking change so it needs to be marked accordingly in the changelog 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Marc Pichler <marc.pichler@dynatrace.com>
LogRecord
to be an interfaceLogRecord
to be an interface
LogRecord
to be an interfaceLogRecord
to be an interface
…ry#5749) Co-authored-by: Marc Pichler <marc.pichler@dynatrace.com>
Which problem is this PR solving?
Created an interface for
LogRecord
soLogRecordProcessor#onEmit
consumes the interface instead of the class.Fixes #5736
Related to #5722
Short description of the changes
SdkLogRecord
interface (there already is aLogRecord
in the api-logs so I named this oneSdkLogRecord
to avoid confusion with the log record interface in the api-logs.LogRecord
class toLogRecordImpl
to avoid confusion with the interfaceType of change
Not sure if this would be considered a breaking change.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: