This repository has been archived by the owner on Sep 28, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Issues: ipfs/js-ipfs-http-response
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Tests should not use ipfs
exp/novice
Someone with a little familiarity can pick up
help wanted
Seeking public contribution on this issue
P1
High: Likely tackled by core team if no one steps up
status/ready
Ready to be worked
#31
opened Jan 7, 2020 by
vasco-santos
Sharding support in /ipns/<fqdn> paths
help wanted
Seeking public contribution on this issue
kind/enhancement
A net-new feature or improvement to an existing feature
status/ready
Ready to be worked
#22
opened May 6, 2019 by
lidel
Enable Windows CI on travis
help wanted
Seeking public contribution on this issue
P1
High: Likely tackled by core team if no one steps up
status/ready
Ready to be worked
#21
opened Apr 8, 2019 by
vasco-santos
Replace manual traversal with ipfs.resolve
exp/expert
Having worked on the specific codebase is important
help wanted
Seeking public contribution on this issue
P2
Medium: Good to have, but can wait until someone steps up
status/ready
Ready to be worked
#14
opened Jan 15, 2019 by
lidel
Add tests that assert that the payload is correct
help wanted
Seeking public contribution on this issue
kind/enhancement
A net-new feature or improvement to an existing feature
status/ready
Ready to be worked
#4
opened Aug 1, 2018 by
satazor
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.