Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cancelling a request

Open
  • Is something wrong?
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

Description

discussion enhancement help wanted

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.

Dominant language
Reason
Stars
52
Forks
1
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from lessp/fetch

All issues in lessp/fetch

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.