Skip to content

Commit 351f967

Browse files
authored
chore(relay): Remove stale comment about span.name (#4835)
As of #4796, the `op` field on `SpanV1` does _not_ contain the name, it contains the op! So, this comment is no longer true, there's no duplication.
1 parent 7200f0f commit 351f967

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

relay-spans/src/v2_to_v1.rs

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -99,10 +99,8 @@ pub fn span_v2_to_span_v1(span_v2: SpanV2) -> SpanV1 {
9999
}
100100
}
101101

102-
// Note: This writes the incoming `name` field to a the `sentry.name` attribute. This creates a
103-
// bit of duplication, since the attribute `sentry.name` will have the same value as the `op`
104-
// field. This duplication is temporary, since we will soon generate a proper `op` field that will
105-
// be different from the name.
102+
// Write the incoming `name` field to a the `sentry.name` attribute, since the V1
103+
// Span schema doesn't have a top-level `name` field.
106104
if let Some(name) = name.value() {
107105
data.insert(
108106
"sentry.name".to_owned(),

0 commit comments

Comments
 (0)