-
Notifications
You must be signed in to change notification settings - Fork 55
chore: migrate network tracking to zen observable #1373
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
chore: migrate network tracking to zen observable #1373
Conversation
…tude-TypeScript into no-ticket-zen-observable-dead-click
…tude-TypeScript into no-ticket-zen-observable-dead-click
…tude-TypeScript into no-ticket-zen-observable-dead-click
Co-authored-by: Copilot <[email protected]>
…ack-dead-click.test.ts Co-authored-by: Copilot <[email protected]>
…ack-dead-click.test.ts Co-authored-by: Copilot <[email protected]>
…itude/Amplitude-TypeScript into AMP-142601-migrate-network-tracking-to-zen-observable
…tude-TypeScript into AMP-142601-migrate-network-tracking-to-zen-observable
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.
LGTM!
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.
Just notes for myself: it makes sense to delete subscriptions as we only push one to it.
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.
Yeah I had originally copy-pasted this logic from another autocapture (which had several subscriptions) to network capture. Didn't realize that network only had the one subscription.
82f0e00
into
zen-observable-migration
Summary
Remove RxJS from "plugin-network-capture-browser"
Checklist