Skip to content
This repository was archived by the owner on Feb 12, 2024. It is now read-only.
This repository was archived by the owner on Feb 12, 2024. It is now read-only.

Tracking issue for ky removal #2801

Activity

self-assigned this
on Mar 2, 2020
pcowgill

pcowgill commented on Mar 9, 2020

@pcowgill
Contributor

@hugomrdias Will this behavior from ky be preserved Treats non-2xx status codes as errors?

added a commit that references this issue on Mar 11, 2020
9bc9625
added a commit that references this issue on Mar 22, 2020
dd42cf8
sholladay

sholladay commented on Apr 15, 2020

@sholladay

Hey, Ky maintainer here. I wanted to see if there is something we could do to make Ky easier to use or better in some way? Looks like you had to re-implement some of Ky's behavior, which is unfortunate. Maybe we could provide an option related to cloning responses? If there are any other bugs that lead to this, I'd love to take a look and fix those since they were blockers for you and might be for other projects, too. Also, since you are using node-fetch now, I'm curious if you considered got?

added a commit that references this issue on Aug 18, 2022
41ea529
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

exp/expertHaving worked on the specific codebase is importantpkg:http-clientIssues related only to ipfs-http-clientstatus/in-progressIn progress

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    Participants

    @hugomrdias@pcowgill@sholladay

    Issue actions

      Tracking issue for `ky` removal · Issue #2801 · ipfs/js-ipfs