-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Attach top level domain to Failed to fetch
errors.
#15709
Comments
Not 100% sure on the following, but in order not to explode grouping in some cases I would maybe do just the domain name. So |
Failed to fetch
errors.Failed to fetch
errors.
Closes #15709 This also adds tests for the various types of TypeErrors that fetch can produce.
Closes #15709 This also adds tests for the various types of TypeErrors that fetch can produce.
Closes #15709 This also adds tests for the various types of TypeErrors that fetch can produce.
Closes #15709 This also adds tests for the various types of TypeErrors that fetch can produce.
One thing to watch out for, many domains are not two parts, ex: |
oh crap that is actually pretty annoying |
Description
To make
Failed to fetch
errors without any further error description (mostly for ad-blocked requests) more actionable we want to include the fetch domain to the issue itself.e.g.
TypeError: Failed to fetch
would becomeTypeError: Failed to fetch (some-blocked-third-party.io)
The text was updated successfully, but these errors were encountered: