Skip to content

RUM-19153: Migrate readers to shared RUM context - #4027

Merged
kikoveiga merged 1 commit into
developfrom
kikoveiga/RUM-19153/use-typed-rum-context
Oct 26, 2026
Merged

kikoveiga merged 1 commit into
developfrom
kikoveiga/RUM-19153/use-typed-rum-context

Conversation

@kikoveiga

@kikoveiga kikoveiga commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

What does this PR do?

Migrates the remaining Android RUM context readers in Flags, Profiling, Trace, WebView, and Session Replay to the shared typed RumContext introduced in #4019. Replay and WebView cache the typed snapshot instead of the mutable feature map.

Motivation

RUM-19153: replace repeated field parsing with shared types, preparing for the context changes in #3970. #4019 has merged; this PR now targets develop.

Additional Notes

Legacy flat fields remain published for cross-platform consumers, including Flutter Session Replay. Updated tests use typed-only contexts. Affected unit and JVM integration suites, formatting, Detekt, and generated-file checks passed.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

@datadog-prod-us1-5

datadog-prod-us1-5 Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Pipelines  Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 68.29%
• Overall Coverage: 71.84% (-0.04%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 40fe938 | Docs | View more details | Give us feedback!

@kikoveiga
kikoveiga added this pull request to stack #4028 October 22, 2026 10:55
@kikoveiga
kikoveiga force-pushed the kikoveiga/RUM-19153/use-typed-rum-context branch from cdbf208 to 6c37d17 Compare October 23, 2026 08:53
Base automatically changed from kikoveiga/RUM-17009/extract-shared-rum-context to develop October 23, 2026 10:57
@kikoveiga
kikoveiga force-pushed the kikoveiga/RUM-19153/use-typed-rum-context branch 2 times, most recently from f4f6e96 to e9ae12a Compare October 23, 2026 11:22
@kikoveiga

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T16:09:54.065887Z 40fe938 New commits
🔒 Security Review ✅ Completed 2026-10-23T16:11:05.779028Z 40fe938 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 👍

Reviewed commit: e9ae12aac4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: e9ae12aac4

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@kikoveiga
kikoveiga force-pushed the kikoveiga/RUM-19153/use-typed-rum-context branch 7 times, most recently from fe11ef3 to 4915b79 Compare October 23, 2026 14:05
@kikoveiga

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. You're on a roll.

Reviewed commit: 4915b79780

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 4915b79780

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@kikoveiga
kikoveiga marked this pull request as ready for review October 23, 2026 14:31
@kikoveiga
kikoveiga requested review from a team as code owners October 23, 2026 14:31

@datadog-prod-us1-5 datadog-prod-us1-5 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bits Code Review: PASS

More details

The shared RUM publisher supplies the values expected by the migrated readers, while legacy flat fields remain available to cross-platform consumers. The completed static review identified no actionable regression.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 4915b79

0xnm
0xnm previously approved these changes Oct 23, 2026

@0xnm 0xnm left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

worth getting one more approval

@kikoveiga
kikoveiga force-pushed the kikoveiga/RUM-19153/use-typed-rum-context branch from 4915b79 to 40fe938 Compare October 23, 2026 16:06
@kikoveiga kikoveiga added the ready-for-human-review All agentic review feedback was addressed and PR is ready for the human review. label Oct 25, 2026
@kikoveiga
kikoveiga requested a review from 0xnm October 26, 2026 12:10
@kikoveiga
kikoveiga merged commit baa806b into develop Oct 26, 2026
28 checks passed
@kikoveiga
kikoveiga deleted the kikoveiga/RUM-19153/use-typed-rum-context branch October 26, 2026 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-human-review All agentic review feedback was addressed and PR is ready for the human review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants