-
Notifications
You must be signed in to change notification settings - Fork 375
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
W3C: Propagate unknown values as-is #2485
Conversation
d7e0870
to
b7e6c91
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.
The change looks reasonable, although this is one of those PRs that it's probably best someone from tracing give a second pass as I understand the code changes, but I don't understand if they are the correct code changes for the outcome we want ;)
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.
Looks great!
end | ||
end | ||
|
||
[origin, sampling_priority, tags] | ||
[origin, sampling_priority, tags, unknown_fields] |
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.
Perhaps we should extract this to its own object, if the array keeps on growing. It feels weird to me that the caller need to understand the index of the array to get the corresponding value.
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'll do it if we get to 5! 🦆
Unknown Datadog-specific fields should be propagated as-is, as they might belong to future versions Datadog Tracers.
ddtrace
's job is to simply pass the them downstream with the same incoming values.