Skip to content

feat(types): Upstream some replay types #6506

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

Merged
merged 4 commits into from
Jan 3, 2023
Merged

feat(types): Upstream some replay types #6506

merged 4 commits into from
Jan 3, 2023

Conversation

mydea
Copy link
Member

@mydea mydea commented Dec 13, 2022

This PR upstreams some types from @sentry/replay to @sentry/types, in preparation for moving some stuff there.
Especially the ReplayEvent may still change a bit, but I think this should be fine.

@mydea mydea added Package: types Package: replay Issues related to the Sentry Replay SDK labels Dec 13, 2022
@mydea mydea requested review from billyvg and Lms24 December 13, 2022 08:59
@mydea mydea self-assigned this Dec 13, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 13, 2022

size-limit report 📦

Path Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified) 19.81 KB (+0.11% 🔺)
@sentry/browser - ES5 CDN Bundle (minified) 61.34 KB (+0.06% 🔺)
@sentry/browser - ES6 CDN Bundle (gzipped + minified) 18.58 KB (+0.1% 🔺)
@sentry/browser - ES6 CDN Bundle (minified) 54.93 KB (+0.16% 🔺)
@sentry/browser - Webpack (gzipped + minified) 20.34 KB (+0.01% 🔺)
@sentry/browser - Webpack (minified) 66.46 KB (-0.05% 🔽)
@sentry/react - Webpack (gzipped + minified) 20.36 KB (+0.02% 🔺)
@sentry/nextjs Client - Webpack (gzipped + minified) 47.62 KB (+0.12% 🔺)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified) 26.76 KB (+0.05% 🔺)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified) 25.2 KB (+0.07% 🔺)
@sentry/replay ES6 CDN Bundle (gzipped + minified) 42.09 KB (+0.01% 🔺)
@sentry/replay - Webpack (gzipped + minified) 38.17 KB (0%)

@@ -942,6 +942,7 @@ export class ReplayContainer implements ReplayContainerInterface {
trace_ids: traceIds,
urls,
replay_id: replayId,
event_id: replayId,
Copy link
Member

Choose a reason for hiding this comment

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

I don't think this is what we want as we will then have multiple replay events with the same event id?

Copy link
Member

Choose a reason for hiding this comment

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

I think we can get of this line, right? The uuid is assigned in _prepareEvent.

Copy link
Member Author

Choose a reason for hiding this comment

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

done!

Comment on lines +137 to +191
replay_event: 'replay_event',
replay_recording: 'replay_recording',
Copy link
Member

Choose a reason for hiding this comment

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

damn we should have named these replay and recording to be consistent with our other event types

Copy link
Member

@Lms24 Lms24 left a comment

Choose a reason for hiding this comment

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

LGTM apart from the event_id as mentioned by Billy.

@mydea mydea merged commit a23bda5 into master Jan 3, 2023
@mydea mydea deleted the fn/replay-types branch January 3, 2023 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Package: replay Issues related to the Sentry Replay SDK
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants