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
In createBundleLinksForManifest: in ZincBundleCloneTask.m, I noticed the file manager calls linkItemAtPath:toPath:error, which leaves a copy of the asset in the objects directory and a copy in the bundle directory thus taking up twice the storage space.
Any compelling reason why this is preferred over moveItemAtPath:toPath:error:? I assumed it was for caching purposes if the network was interrupted during the cloning, but I didn't see a cleanup task being performed after the clone was complete. I'll admit I didn't dive too far into the code, but at first glance I was wondering what the preferred way to clean up directory was?
The text was updated successfully, but these errors were encountered:
In
createBundleLinksForManifest:
in ZincBundleCloneTask.m, I noticed the file manager callslinkItemAtPath:toPath:error
, which leaves a copy of the asset in the objects directory and a copy in the bundle directory thus taking up twice the storage space.Any compelling reason why this is preferred over
moveItemAtPath:toPath:error:
? I assumed it was for caching purposes if the network was interrupted during the cloning, but I didn't see a cleanup task being performed after the clone was complete. I'll admit I didn't dive too far into the code, but at first glance I was wondering what the preferred way to clean up directory was?The text was updated successfully, but these errors were encountered: