Closed dj-stormtrooper closed 11 months ago
That would be fine (but not necessary) as long as comments make it obvious that it's primarily meant to support URL.
Yeah, I think we can keep it more specific, there is no need for a flexible solution here
I can accept this as is.
Great, thanks!
@waltjones any chance we can get a new version of this package released that includes this change? I've been debugging why my project didn't have any paths in the network telemetry events and this PR looks like it would fix it. We use fetch
with URL
objects as the first parameter.
@goibon Released: https://github.com/rollbar/rollbar.js/releases/tag/v2.26.3
Apologies for the delay.
Description of the change
At Fingerprint.js we have experienced several issues with our customers who use Rollbar. Some telemetry events weren't captured due to unsupported
URL
type infetch
/XHR
(see Parameter section - theURL
type is valid argument type forfetch
).I added support to rollbar
Instrumenter
and covered this behaviour with unit tests.fetch
andXHR
support any object with stringifier, so I can extend this condition to any object withtoString
method, thought it might be not really useful. Feel free to discuss the solutionType of change
Related issues
I didn't create particular issue for Rollbar, but It's similar to what had with Honeybadger: issue, PR
Checklists
Development
Code review