Skip to content

fix: Set last_event_id only for error events#1767

Merged
sl0thentr0py merged 2 commits intomasterfrom
neel/fix-last-event-id
Mar 21, 2022
Merged

fix: Set last_event_id only for error events#1767
sl0thentr0py merged 2 commits intomasterfrom
neel/fix-last-event-id

Conversation

@sl0thentr0py
Copy link
Copy Markdown
Member

last_event_id only has a valid use case for cross-referencing errors on the end-user UI, updating it for transactions doesn't make sense and is consistent with python.

Fixes #1766

@sl0thentr0py sl0thentr0py requested a review from st0012 March 18, 2022 22:20
end

@last_event_id = event&.event_id
@last_event_id = event&.event_id unless event.is_a?(Sentry::TransactionEvent)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sl0thentr0py this is the reason I want to do the inheritance-removal refactor. they are basically 2 types of events but yet they're both Sentry::Event.

Copy link
Copy Markdown
Contributor

@st0012 st0012 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you add a changelog entry for this? thx

@st0012 st0012 added this to the 5.3.0 milestone Mar 19, 2022
@sl0thentr0py sl0thentr0py merged commit 9ed47c9 into master Mar 21, 2022
@sl0thentr0py sl0thentr0py deleted the neel/fix-last-event-id branch March 21, 2022 11:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

last_event_id references transaction event

2 participants