You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behaviour is last-file-wins for both go-IPFS and js-IPFS.
Should this be the case or should they error? The API makes it trivial to do this kind of operation, but file systems typically do not support entries with duplicate names.
Once there is an agreement, this should be documented in the spec order for DAGs to be recreated without reference to go-IPFS or js-IPFS.
The text was updated successfully, but these errors were encountered:
Following on from ipfs/js-ipfs#2622
You can have the situation where a user tries to build a UnixFS directory with duplicate paths:
Current behaviour is last-file-wins for both
go-IPFS
andjs-IPFS
.Should this be the case or should they error? The API makes it trivial to do this kind of operation, but file systems typically do not support entries with duplicate names.
Once there is an agreement, this should be documented in the spec order for DAGs to be recreated without reference to
go-IPFS
orjs-IPFS
.The text was updated successfully, but these errors were encountered: