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
Add a built-in storage provider that is initialized with a fileURL, to accomodate the following use cases:
a fileURL provided by NSDocument, UIDocument, or SwiftUI document-based APIs that points to a location on disk (for example, .fileImporter that returns a fileURL that then needs to be accessed as a security scoped URL - .startAccessingSecurityScopedResource())
I'm not sure if this would be right for the default file storage provider, but I've been playing with making NSDocument write to a bundle format using the general design suggested here for CloudKit .
The nice feature of this is that the format should then automatically merge. So for example you can share this on iCloud Drive and concurrent edits should converge.
Except my version seems to have bugs that I'm still figuring out :) Anyway, don't have anything fully working to share yet, just wanted to add this note for possible future implementation.
If you want to lift the logic, there's an implementation of the "partial incremental changes"/"compacted changes" in parallel in the DocumentStorage class of the repo - Following the JS impl, it was meant to ride about the provider, which is only concerned with shifting bytes onto, and off of, disk given various prefixes (used to determine locations)
Add a built-in storage provider that is initialized with a fileURL, to accomodate the following use cases:
.startAccessingSecurityScopedResource()
)The text was updated successfully, but these errors were encountered: