-
Notifications
You must be signed in to change notification settings - Fork 159
example: turn directory into UnixFS DAG #663
Copy link
Copy link
Open
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps updif/easySomeone with a little familiarity can pick upSomeone with a little familiarity can pick upeffort/hoursEstimated to take one or several hoursEstimated to take one or several hoursgood first issueGood issue for new contributorsGood issue for new contributorshelp wantedSeeking public contribution on this issueSeeking public contribution on this issue
Description
Metadata
Metadata
Assignees
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps updif/easySomeone with a little familiarity can pick upSomeone with a little familiarity can pick upeffort/hoursEstimated to take one or several hoursEstimated to take one or several hoursgood first issueGood issue for new contributorsGood issue for new contributorshelp wantedSeeking public contribution on this issueSeeking public contribution on this issue
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
We have many unixfs implementations, and it is extremely confusing for new developers to understand what they should use and why. (cc @2color)
Proposed improvement
The ./exmaples should have an example of
ipfs add + ipfs dag exportequivalent for reading a file or a directory from local filesystem, and turning it into a CAR with UnixFS DAG that was properly chunked / HAMT-sharded.The example should be a CLI tool that accepts same flags as
ipfs add, demonstrating how to adjust chunker, hash function, or decide if mode/mtime should be preserved.