iodide-project/iodide

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

Open

#1,396 创建于 2019年1月18日

在 GitHub 查看
 (8 评论) (0 反应) (0 负责人)JavaScript (1,483 star) (147 fork)batch import
good first issue

描述

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

贡献者指南

技术栈
javascript
领域
frontenddocumentation
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
无
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
70
研究方向
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.