Skip to content
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

fix: Add event type to item header when envelopes are forced #3676

Merged
merged 1 commit into from
Jun 15, 2021

Conversation

kamilogorek
Copy link
Contributor

An oversight that prevents tunnel from working correctly. In the times when there was only a single event type, we didn't specify event.type === 'event' because it was redundant. Now it's not.

@kamilogorek kamilogorek requested review from a team, AbhiPrasad and vladanpaunovic and removed request for a team June 15, 2021 08:28
@github-actions
Copy link
Contributor

size-limit report

Path Size
@sentry/browser - CDN Bundle (gzipped) 20.97 KB (-0.01% 🔽)
@sentry/browser - Webpack 21.84 KB (+0.01% 🔺)
@sentry/react - Webpack 21.88 KB (+0.01% 🔺)
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped) 28.36 KB (0%)

@kamilogorek kamilogorek merged commit 96c36e8 into master Jun 15, 2021
@kamilogorek kamilogorek deleted the envelope-event-type branch June 15, 2021 08:40
@@ -47,7 +47,7 @@ export interface Event {
}

/** JSDoc */
export type EventType = 'transaction';
export type EventType = 'event' | 'transaction';
Copy link
Contributor

Choose a reason for hiding this comment

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

I thought this EventType refer to Error, Transaction, Default? Which unfortunately might not match envelope header requirements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants