Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add
data
field to the Event interface #4575Add
data
field to the Event interface #4575Changes from 5 commits
2b59dad
1342cd0
a302e9e
f0cc15e
0053c00
0149ed2
a33b8e8
e5fa009
60e5810
f215a17
712493e
5c5678d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I think it's also a little confusing when we use the type
LogAttributeValue
for the body the logs bridge API. Should we use something namedLogRecordBody
(or similar) instead? Another option may be to create a type AnyValue and have LogAttributeValue be an alias to that. 🤔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.
LogAttributeValue
is currently defined along withLogAttributes
like this:I like the idea of introducing
AnyValue
type as part of the common API, but then we would need to also define something in place ofLogAttributes
, maybeAnyValues
orAnyValueMap
?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.
Ah, I see. Yes, I think the option you proposed with
AnyValue
andAnyValueMap
works best.Looked at another repo: In Java, they call it KeyAnyValueList, leaning on the name from protobuf. That's unfortunately not applicable for us the attributes are not organized as a list.
KeyAnyValueMap
would feel redundant as it's implicit that there's a key in a map. So I'm leaning towardsAnyValueMap
as you suggested. 🙂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.
I have added the AnyValue and AnyValueMap types to the core API. I think this a breaking change for the API, and I have updated its changelog accordingly.
I have also changed the LogRecord body type to
LogBody
. I consideredLogRecordBody
, but we already usedLogAttributes
for attributes, so I wanted to be consistent.