Conversation
Format spans in format expected by Test Engine.
Align type with Test Engine, simplify implementation. Make pylint happy
d286f98 to
0ea0fa4
Compare
nprizal
left a comment
There was a problem hiding this comment.
Hi @scadu, thanks for opening the PR. It looks great! I appreciate you adding the codedoc around the expected data structure for span details.
We’re planning to implement validation to prevent the collector from sending invalid span data but we’ll open a separate PR for that.
nprizal
left a comment
There was a problem hiding this comment.
Thanks for adding the validation 💚 . I think we want the detail to be required for sql, http, and annotation. Is that right @gchan @malclocke?
Yep that's correct. Here's the reference which should be up-to-date and correct. |
Co-authored-by: Naufan P. Rizal <np.rizal@icloud.com>
|
Thanks for the review @nprizal! I think it should be good to merge now? |
Format spans in format expected by Test Engine.
Since
detailstype is changed fromstringtodict, this could be a breaking change, even though span details previously wouldn't work due to the type mismatch between collector and Test Engine.