Skip to content
This repository was archived by the owner on Jun 20, 2023. It is now read-only.
This repository was archived by the owner on Jun 20, 2023. It is now read-only.

/<cid>/path/to/file paths are not considered valid paths #19

@kishansagathiya

Description

@kishansagathiya

go-path/path.go

Lines 22 to 27 in 1bd0722

// A Path represents an ipfs content path:
// * /<cid>/path/to/file
// * /ipfs/<cid>
// * /ipns/<cid>/path/to/folder
// * etc
type Path string

but when I try, I see

$ ipfs get /QmbkfHeLFHzKR9723HVgktuFb8dURv9jG2ez6SLq1gjQfG
Error: invalid 'ipfs ref' path
$ ipfs get /QmbkfHeLFHzKR9723HVgktuFb8dURv9jG2ez6SLq1gjQfG/temp2/im.gif
Error: invalid 'ipfs ref' path

Either description should be changed or we should start accepting those paths. I am in favour of adding support for that path pattern, but I wonder if accepting those paths would create problems for ipfs-based projects.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions