Document types of fetch errors more thoroughly · node-fetch/node-fetch#549

(0 comments) (0 reactions) (0 assignees)JavaScript (8,563 stars) (1,061 forks)batch import

Node-specificgood first issue

説明

There used to be only one type of operational error from node-fetch: FetchError.

This is no longer the case as I can count at least six: Error, NodeError, TypeError, SyntaxError, AbortError and FetchError. All of them can be triggered in one way or another through invalid response.

We would like to unify them in some ways but it's (a) a breaking change, (b) sometimes not standard compliant (see #498).

So for those we can't wrap with FetchError in next major release, the doc needs to be updated:

https://github.com/bitinn/node-fetch/blob/master/ERROR-HANDLING.md

コントリビューターガイド

技術スタック: javascriptnodejs
領域: documentation
Issue 種別: documentation
難度: 2
推定時間: under 1 hour
活動状況: stale
明確さ: clear
前提条件: Familiarity with node fetch
初心者向け度: 80
調査方針: The issue requests updating the ERROR HANDLING.md file to document all possible error types from node fetch, including Error, NodeError, TypeError, SyntaxError, AbortError, and FetchError. The fix involves adding descriptions and examples for each error type. The issue has been open since 2018 with no recent activity, so it's a good candidate for a first time contributor to pick up.