feat(replay): Start bringing in new replay context wrappers to test #91982
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.
The original replay context is a big ball of logic and hacks. It's hard to use and mixes a lot of responsibilities.
A while ago I wrote some smaller context providers to break things up, and remove some old hacks that are no longer needed now, either because rrweb improvements, and because some of the problems were self-inflicted (like some perf hacks, and just doing things the wrong way around).
So this is the first PR to wrap players with the new providers, and to swap out a couple places that use the old context, for calls into the new context. What's apparent already within this PR is that the new context will push
current timere-renders down the react tree. I need to followup and edit a bunch more places before this will be functional, but in the mean time the providers will be a no-op because the new feature-flag is guarding the interaction points.