-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat: incremental updates for mobile transformer #19567
feat: incremental updates for mobile transformer #19567
Conversation
Size Change: 0 B Total Size: 2 MB ℹ️ View Unchanged
|
More like a question, since we have synthetic IDs, what if the removed/updated wireframe is a synthetic ID? Would that work the way how it is implemented? I believe the synthetic IDs are just the nested components right? For example, a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a comment but otherwise LGTM
if (convertedEl !== null) { | ||
acc.push(convertedEl) | ||
} | ||
return acc | ||
}, [] as serializedNodeWithId[]) | ||
} | ||
|
||
function isMobileIncrementalSnapshotEvent(x: unknown): x is MobileIncrementalSnapshotEvent { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feels like this does a little more than just checking the type on the event
function isMobileIncrementalSnapshotEvent(x: unknown): x is MobileIncrementalSnapshotEvent { | |
function isValidMobileIncrementalSnapshotEvent(x: unknown): x is MobileIncrementalSnapshotEvent { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm, I want to split this up more so I'm going to punt this into the future
first pass at adding incremental mutations created some fake mobile recordings locally and these behaved as expected this adds: removals these can be passed through - they're the same as rrweb adds the added wireframes can be converted just like in full snapshots (I think) updates these are implemented as removes and then adds this might not work on recordings with very many mutations but it'll be at least enough for us to get some folk testing it and we should have few enough mutations that it'll be ok
* master: (94 commits) feat: Add cta on billing for >20k annual spend customers (#19508) refactor(temporal/squash): Support flat person override table in squash workflow (#19347) fix(surveys): remove link in user interview template (#19584) feat: populate plugin capabilities on install and edit (#19188) chore: Make plugin-server ignore deleted plugin configs (#18444) chore: Add Flutter feature flags snippets (#19563) fix(bi): fixed some of the query duplications (#19573) fix: assume typeless series nodes are of type events node (#19550) chore(deps): bump chromaui/action from 1 to 10 (#19560) fix(trends): fix breakdowns persons label (#19534) fix(trends): fix breakdown legend (#19533) feat: incremental updates for mobile transformer (#19567) chore(deps): bump peter-evans/find-comment from 1 to 2 (#19559) chore(data-warehouse): cleanup unused celery code and extend time (#19568) Revert "feat(data-warehouse): hubspot integration" (#19569) feat(data-warehouse): hubspot integration (#19529) feat: Feature gate session replay controls using available_product_features (#19401) fix: Padding on bullet lists (#19565) chore: Post 3000 LemonButtton cleanup (#19540) chore(deps): bump aws-actions/amazon-ecr-login from 1 to 2 (#19558) ...
first pass at adding incremental mutations
created some fake mobile recordings locally and these behaved as expected
this adds: