-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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: show network payloads #18562
feat: show network payloads #18562
Conversation
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
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.
Would love to try this myself after we have the JS changes in for testing but overall it looks fantastic
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated3 snapshot changes in total. 0 added, 3 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
@neilkakkar want to review decide changes? |
rrweb has network payloads queued up as a feature... but it's taking a while. The easiest way to test it is to adopt it ourselves. This adds a copy of the plugin proposed for rrweb, and uses it to wrap xhr and fetch. We can match performance timings and these new NetworkRequests based on URL and timings used by PostHog/posthog#18562 for now this can only be enabled via decide response, which allows header and body capture to be configured separately, that config is only enabled via flag while we test internally
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.
thanks for asking, looks good!
You are now a pro at decide changes xD
Once we can capture payloads and status codes reliably... we need to show them to people.
This does that...
needs PostHog/posthog-js#886
config