margelo / margelo/react-native-nitro-fetch

Parts of Fetch API not implemented

Open
#8 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
997
Forks
50
Avg merge
1d 20h
Merged PRs (30d)
14

Description

Before submitting a new issue
  • I tested using the latest version of the library, as the bug might be already fixed.
  • I tested using a supported version of react native.
  • I checked for possible duplicate issues, with possible answers.
Bug summary

Quickly tried this out in a fairly big project, and it failed on a few edge cases that I ran into (apparently not edge casey enough):

It's not an exhaustive list, and I'd be down to send a PR if you agree that this is useful.

Library version

0.1.3

Environment info
N/A
Steps to reproduce
Reproducible example repository

N/A

Contributor guide

Open the contributing guide

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

Locate the library's Fetch API implementation and examine how Headers and Response are currently exposed. Use the linked MDN behavior as the reference, then add coverage for response.headers.get() and Response.clone(); done means both reported gaps work in the supported React Native environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, react-native
Domain
api, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.