You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling RCTRenderingPerf.stop, we automatically get the output from ReactPerf.printInclusive() and ReactPerf.printWasted(), but have no way of getting ReactPerf.printExclusive(), as it is not exposed by the module.
Reproduction Steps and Sample Code
The following code will trigger the output from printInclusive and printWasted:
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.
Description
When calling
RCTRenderingPerf.stop
, we automatically get the output fromReactPerf.printInclusive()
andReactPerf.printWasted()
, but have no way of gettingReactPerf.printExclusive()
, as it is not exposed by the module.Reproduction Steps and Sample Code
The following code will trigger the output from
printInclusive
andprintWasted
:Solution
Expose the output functions to be called directly instead of automatically calling some inside stop.
I am happy to do a merge request for this.
Additional Information
The text was updated successfully, but these errors were encountered: