-
Notifications
You must be signed in to change notification settings - Fork 118
feat(ipld/unixfs): DagModifier: allow specifying MaxLinks per file #898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure that we are going to make immediate use of this, but probably good to have.
Most immediate usecase would be to support MaxLinks in MFS if we wanted.
On second thoughts, we might need this since adding uses MFS.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this value ever written anywhere? Is not, maybe better to just use a const so everyone knows it is a fixed read-only value. Otherwise LGTM.
lgtm, we will expose it as configuration option, part of ipfs/kubo#10751 |
@@ -46,6 +46,7 @@ type DagModifier struct { | |||
|
|||
Prefix cid.Prefix | |||
RawLeaves bool | |||
MaxLinks int |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hsanjuan is this enough, given we've added separate setting for HAMT? (#897 (review))
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is probably enough since this seems to deal only with files...
cc ipfs/kubo#10751