iodide-project/iodide

add link to docs in fetch error messages (in case of CORS)

Open

#1,396 opened on Jan 18, 2019

View on GitHub
 (8 comments) (0 reactions) (0 assignees)JavaScript (1,483 stars) (147 forks)batch import
good first issue

Description

CORS issues are tricky and confusing. it would be great if we could let people know if they are hitting a CORS error in particular (rather than a fetch error in general) when they run into a CORS problem, and direct them to help / workarounds / more info.

(in investigating this, we might find that there are other kinds of errors we can surface/specify)

cc @hamilton

Contributor guide

Tech stack
javascript
Domain
frontenddocumentation
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Look for the code where fetch errors are handled, likely in a utility module or the main application logic. Identify where fetch errors are caught and modify the error message to detect CORS errors (e.g., checking for TypeError or specific status codes). Add a link to documentation about CORS workarounds. Review comments in the issue for further guidance.