Stash background trace directly in HostTarget, simplify API #55347
+315
−149
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.
Summary:
Changelog: [Internal]
Moves state and logic related to stashing a background trace from
JReactHostInspectorTarget(JNI wrapper boilerplate, Android-specific) toHostTarget(cross-platform C++).Managing the full lifecycle of a background trace inside
HostTargetlets us remove a fair amount of API surface:HostTargetDelegate::unstable_getHostTracingProfileThatWillBeEmittedOnInitialization()HostTarget::hasActiveSessionWithFuseboxClient()TracingAgent::emitExternalHostTracingProfile()We also refactor some of the surrounding code and add tests (previously missing) for the behaviour of stashed background traces when there is more than one session.
Reviewed By: huntie
Differential Revision: D91589884