feat(replay): Deprecate Replay, ReplayCanvas, Feedback classes #10270
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.
Instead, users should use the new functional styles.
Note that we'll probably actually un-deprecate
Replay
in some form in v8, as we'll be keeping the class around there for sure (as there is a lot of logic in there...). But users should not use it, so deprecating this now!While at it, I also deprecated the old
InitSentryForEmber
method in favor ofinit()
.It's slightly unfortunate that I missed this, but we probably shouldn't have exposed
ReplayCanvas
as a class anymore at all 😬 maybe we wait before we document this etc. until we merged the functional style. cc @billyvg