[Flight] Bypass caches in Flight fixture if requested #33445
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
When the "Disable cache" checkbox is checked in the dev tools, we should bypass the caching of the 3rd-party component in the Flight fixture. This allows us to quickly compare the different output (with and without caching) in React's custom performance tracks.
github-actions
bot
added
the
React Core Team
|
Comparing: b4477d3...c586560 Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
unstubbable
force-pushed
the
flight-fixture-bypass-cache
branch
from
7f912d1 to
c586560
Compare
sebmarkbage
approved these changes
Jun 6, 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.
When the "Disable cache" checkbox is checked in the dev tools, we should bypass the caching of the 3rd-party component in the Flight fixture. This allows us to quickly compare the different output (with and without caching) in React's custom performance tracks.