ipfs/kubo

Files API should handle ipfs protocol paths

Open

#2,837 opened on Jun 11, 2016

View on GitHub
 (2 comments) (2 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
exp/novicehelp wantedkind/enhancementstatus/deferred

Description

As files API provides functions not available elsewhere (ipfs fiels stat) it would be great if it was handling /ipfs/Qm...AAA paths also.

They are already not fully functional (you can't for example copy files from /ipfs/ directory in files API).

This extends to: /ipns/ and other if they are ever created.

Contributor guide

Tech stack
go
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingIPFS basicsMFS concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The contributor should start by understanding the existing Files API in the 'core/commands/files' directory and the Mutable File System (MFS) implementation. They need to see how paths like '/ipfs/' are currently handled (likely not at all) and propose changes to integrate IPFS path resolution into the Files API. The issue mentions that copying files from '/ipfs/' directory is not possible, so the solution likely involves adding support for IPFS protocol paths in the files commands. They should read the two existing comments on the issue for any additional context.