-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat: Give access to XHR requests body in breadcrumb hint #2904
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
size-limit report
|
| return; | ||
| } | ||
|
|
||
| // Poor man implementation of ES6 `Map` by tracking and keeping in sync key and value separately. |
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.
Could concurrent requests get this "map" out of sync? I think not, no pre-emption.
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.
Nah, it's not Go 😅
|
Would it be possible to make this configurable? Including XRH request bodies at my org would be a no-go since they often will contain PHI that we can't log. We'd basically have to turn off breadcrumbs entirely. |
|
great -- thanks @kamilogorek ! |
This simplifies the implementation of XHR request body harvesting for breadcrumbs, introduced in #2904. Instead of caching the data and grabbing it at a later point, this grabs it as soon as it's available, in the xhr `send` method.
Closes #2166