javascript-tutorial / javascript-tutorial/en.javascript.info
`Fetch: Cross-Origin Requests` article wording
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 25.5k
- Forks
- 4k
- PR merge metrics
- No merged PRs in 30d
Description
Article: Fetch: Cross-Origin Requests
-
https://github.com/javascript-tutorial/en.javascript.info/blob/285083fc71ee3a7cf55fd8acac9c91ac6f62105c/5-network/05-fetch-crossorigin/article.md?plain=1#L206 This line gives an idea that there can only be three headers when, in fact, there can be more, as per this MDN article or verified in practice.
-
https://github.com/javascript-tutorial/en.javascript.info/blob/285083fc71ee3a7cf55fd8acac9c91ac6f62105c/5-network/05-fetch-crossorigin/article.md?plain=1#L212 A successful response to a preflight request is restricted to an ok-status, which includes 200 but not limited to it, as per the spec.
I may be nitpicking, but I had to google what was wrong with my preflight request when it had ~10 headers and received a 204 response.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open 5-network/05-fetch-crossorigin/article.md and inspect the wording around lines 206 and 212. Compare those statements with the linked MDN article and Fetch specification. Done means the article no longer implies exactly three headers or only a 200 response, while retaining accurate guidance about successful preflight responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100