-
-
Notifications
You must be signed in to change notification settings - Fork 511
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
Correct type attribute's usages #1354
Conversation
bf5735f
to
a7427aa
Compare
b01106c
to
4368fda
Compare
Codecov Report
@@ Coverage Diff @@
## master #1354 +/- ##
==========================================
+ Coverage 98.08% 98.68% +0.59%
==========================================
Files 208 113 -95
Lines 9162 5327 -3835
==========================================
- Hits 8987 5257 -3730
+ Misses 175 70 -105
Continue to review full report at Codecov.
|
Adding @rhcarvalho to double-check this. |
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 good to me, one minor suggestion below to clarify on the item type.
4368fda
to
992520a
Compare
Normal events shouldn't have the `type` field. Only transactions should have `type: "transaction"`. But in the logs, we should still print normal events' type as `"event"`. For more information about the rules, please see https://github.com/getsentry/sentry-ruby/pull/1336/files#r596851969
992520a
to
3cdf077
Compare
Based on this discussion, normal events shouldn't have the
type
attribute and only transaction events should havetype: "transaction"
.So this PR:
type: "event"
from normal eventsTransport
's envelope generation logic: envelope's type is not equivalent to event's type