lessp / lessp/fetch

Cancelling a request

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion enhancement help wanted
Dominant language
Reason
Stars
52
Forks
1
No merged PRs in 30d

Description

May be something for further down the road (or not at all), but logging to remember it!

both fetch and e.g. axios use a similar API. Seeing as reason-fetch bases many of its decisions from whatwg, it might be an idea to go with a similar API (AbortSignal) to that.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by reading the existing reason-fetch request API, then compare its cancellation behavior with the WHATWG Fetch and axios references; done requires a decided AbortSignal-compatible cancellation design and an agreed implementation scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, ocaml
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.