-
-
Couldn't load subscription status.
- Fork 4.5k
feat(replay): Calculate hydration diff timestamps based on related hydration breadcrumbs #73095
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…dration breadcrumbs
Bundle ReportChanges will decrease total bundle size by 1.33kB ⬇️
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #73095 +/- ##
==========================================
+ Coverage 70.83% 77.98% +7.15%
==========================================
Files 6629 6619 -10
Lines 295890 295061 -829
Branches 50965 50830 -135
==========================================
+ Hits 209585 230100 +20515
+ Misses 79293 58653 -20640
+ Partials 7012 6308 -704
|
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
This is the 2nd try at #72561
The original was reverted in 986296c because of some errors that popped up:
The difference now is that I've improved the types to include
data.mutations.next. The real but though was that before, inbreadcrumbItem.tsx, we were doing the left/right timestamp math only for crumbs that have that mutations.next field...That problem is fixed now because we're checking the crumb type first, then defer to the new
<CrumbHydrationButton>which will get the offsets and render all at once.Without that fix, we were basically trying to get the left/right offsets for any breadcrumb type, which would easily explode.
Related to #70199