-
Notifications
You must be signed in to change notification settings - Fork 63
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
RUMM-2659 editable additional attributes #1089
RUMM-2659 editable additional attributes #1089
Conversation
8847c50
to
e80ee0e
Compare
I'm not super familiar with the generator but LGTM. |
val logWithoutAttributes = fakeLog.copy(additionalProperties = emptyMap()) | ||
val attributes = forge.aMap { | ||
val logWithoutAttributes = fakeLog.copy(additionalProperties = mutableMapOf()) | ||
val attributes = forge.aMap<String, Any?> { |
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.
why explicit type is needed now?
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.
Because the compiler can't resolve it
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.
Clear now. I just asked because my IDE was completely fine with removing the type, but after explicit compilation the error was raised indeed.
Codecov Report
@@ Coverage Diff @@
## develop #1089 +/- ##
===========================================
- Coverage 83.27% 83.25% -0.02%
===========================================
Files 273 273
Lines 9342 9344 +2
Branches 1501 1502 +1
===========================================
Hits 7779 7779
- Misses 1146 1149 +3
+ Partials 417 416 -1
|
What does this PR do?
Allow edition of custom attributes for RUM events.
Motivation
The context's additional attributes were immutable by default, meaning there was no way to edit them within the EventMapper callback.