feat(middleware): expose complete React commit timeline - #464
Open
avocado-cb wants to merge 1 commit into
Open
Conversation
Co-authored-by: Codex <codex-noreply@coinbase.com>
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
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.
Description
Adds an additive
commitsfield to the React agentstopProfilingresult. The field contains every captured commit in chronological order with:The existing duration-ranked, size-limited
topSlowCommitsfield remains unchanged for backward compatibility and quick scouting. The React agent documentation and middleware release plan are updated alongside the implementation.Related Issue
Closes #462
Context
stopProfilingcurrently exposes only the slowest commits, even though the normalized React DevTools profile retains the full recording. Downstream performance analysis needs the complete timeline to correlate render bursts and post-process the same commit metadata available to profiler tooling.The timeline is sorted by timestamp, then root id and commit index for deterministic ordering across roots. A regression test covers ordering, metadata, and preservation of the existing slow-commit summary.
Testing
pnpm checks:affectedpnpm test:affectedpnpm release:plan