🏷️ update rum-events-format #3847
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BenoitZugmeyer
force-pushed
the
benoit/update-rum-events-format
branch
from
1dd97f8 to
f2e45db
Compare
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage 🔗 Commit SHA: f2e45db | Docs | Was this helpful? Give us feedback! |
mormubis
approved these changes
Sep 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Update rum-events-format. I'm exceptionally doing this in a separate PR as it introduces a new RUM event which our SDK/types don't expect yet.
Changes
Update types to work around the new RUM "transition" event added to the
RumEventunion. Instead of usingRumEvent, we introduce a newAssembledRumEventthat list only RUM events that are supported / can be assembled by the RUM SDK.Test instructions
If CI pass, it should be fine.
Checklist