Resolve 13608 - Expose RCTRenderingPerf output functions #13610
Closed
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
You currently can not calll
ReactPerf.printExclusive()
when usingRCTRenderingPerf
because it is not exposed directly. See #13608 for full explanation and code sample.This PR exposes all relevant print functions directly, rather than calling some of them inside
stop
.Not sure if this counts a breaking change, as anyone relying on what
stop
does now will get no output any more.Test Plan
To test, add the following debug code to a project:
You will see the different console outputs.