objcjs-types 0.3.0 → 0.5.0

package/dist/FSKit/FSVolumeXattrOperations.d.ts

@@ -1,6 +1,6 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "../Foundation/NSArray.js";
 import type { _NSData } from "../Foundation/NSData.js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { _FSFileName } from "./FSFileName.js";
 import type { _FSItem } from "./FSItem.js";
 import type { FSSetXattrPolicy } from "./FSSetXattrPolicy.js";
@@ -12,15 +12,15 @@ export interface _FSVolumeXattrOperations {
     /**
      * Gets the specified extended attribute of the given item. - Parameters: - name: The extended attribute name. - item: The item for which to get the extended attribute. - reply: A block or closure to indicate success or failure. If getting the attribute succeeds, pass an data instance containing the extended attribute data and a `nil` error. If getting the attribute fails, pass the relevant error as the second parameter; FSKit ignores any data in this case. For an `async` Swift implementation, there's no reply handler; simply return the data or throw an error.
      */
-    getXattrNamed$ofItem$replyHandler$?(name: _FSFileName, item: _FSItem, reply: NobjcObject | null): void;
+    getXattrNamed$ofItem$replyHandler$?(name: _FSFileName, item: _FSItem, reply: ((value: _NSData, error: _NSError) => void) | null): void;
     /**
      * Sets the specified extended attribute data on the given item. - Parameters: - name: The extended attribute name. - value: The extended attribute value to set. This can't be `nil`, unless the policy is ``FSVolume/SetXattrPolicy/delete``. - item: The item on which to set the extended attribute. - policy: The policy to apply when setting the attribute. See ``FSSetXattrPolicy`` for possible values. - reply: A block or closure to indicate success or failure. If setting the attribute fails, pass an error as the one parameter to the reply handler. If setting the attribute succeeds, pass `nil`. For an `async` Swift implementation, there's no reply handler; simply throw an error or return normally.
      */
-    setXattrNamed$toData$onItem$policy$replyHandler$?(name: _FSFileName, value: _NSData | null, item: _FSItem, policy: FSSetXattrPolicy, reply: NobjcObject | null): void;
+    setXattrNamed$toData$onItem$policy$replyHandler$?(name: _FSFileName, value: _NSData | null, item: _FSItem, policy: FSSetXattrPolicy, reply: ((error: _NSError) => void) | null): void;
     /**
      * Gets the list of extended attributes currently set on the given item. - Parameters: - item: The item from which to get extended attributes. - reply: A block or closure to indicate success or failure. If getting the list of extended attributes succeeds, pass the xattrs as an array of ``FSFileName`` instances and a `nil` error. If getting the attriubtes fails, pass `nil` along with the relevant error. For an `async` Swift implementation, there's no reply handler; simply return the byte count or throw an error.
      */
-    listXattrsOfItem$replyHandler$?(item: _FSItem, reply: NobjcObject | null): void;
+    listXattrsOfItem$replyHandler$?(item: _FSItem, reply: ((value: _NSArray, error: _NSError) => void) | null): void;
     /**
      * A Boolean value that instructs FSKit not to call this protocol's methods, even if the volume conforms to it. FSKit reads this value after the file system replies to the `loadResource` message. Changing the returned value during the runtime of the volume has no effect.
      */

package/dist/FSKit/index.d.ts

@@ -112,15 +112,16 @@ export { FSBlockmapFlags } from "./FSBlockmapFlags.js";
 export { FSCompleteIOFlags } from "./FSCompleteIOFlags.js";
 export { FSContainerState } from "./FSContainerState.js";
 export { FSDeactivateOptions } from "./FSDeactivateOptions.js";
+export { FSErrorCode } from "./FSErrorCode.js";
 export { FSExtentType } from "./FSExtentType.js";
 export { FSItemAttribute } from "./FSItemAttribute.js";
 export { FSItemDeactivationOptions } from "./FSItemDeactivationOptions.js";
 export { FSItemID } from "./FSItemID.js";
 export { FSItemType } from "./FSItemType.js";
 export { FSMatchResult } from "./FSMatchResult.js";
+export { FSOperationID } from "./FSOperationID.js";
 export { FSPreallocateFlags } from "./FSPreallocateFlags.js";
 export { FSSetXattrPolicy } from "./FSSetXattrPolicy.js";
 export { FSSyncFlags } from "./FSSyncFlags.js";
 export { FSVolumeCaseFormat } from "./FSVolumeCaseFormat.js";
 export { FSVolumeOpenModes } from "./FSVolumeOpenModes.js";
-export * from "./functions.js";

package/dist/FSKit/index.js

@@ -34,15 +34,16 @@ export { FSBlockmapFlags } from "./FSBlockmapFlags.js";
 export { FSCompleteIOFlags } from "./FSCompleteIOFlags.js";
 export { FSContainerState } from "./FSContainerState.js";
 export { FSDeactivateOptions } from "./FSDeactivateOptions.js";
+export { FSErrorCode } from "./FSErrorCode.js";
 export { FSExtentType } from "./FSExtentType.js";
 export { FSItemAttribute } from "./FSItemAttribute.js";
 export { FSItemDeactivationOptions } from "./FSItemDeactivationOptions.js";
 export { FSItemID } from "./FSItemID.js";
 export { FSItemType } from "./FSItemType.js";
 export { FSMatchResult } from "./FSMatchResult.js";
+export { FSOperationID } from "./FSOperationID.js";
 export { FSPreallocateFlags } from "./FSPreallocateFlags.js";
 export { FSSetXattrPolicy } from "./FSSetXattrPolicy.js";
 export { FSSyncFlags } from "./FSSyncFlags.js";
 export { FSVolumeCaseFormat } from "./FSVolumeCaseFormat.js";
 export { FSVolumeOpenModes } from "./FSVolumeOpenModes.js";
-export * from "./functions.js";

package/dist/FileProvider/NSFileProviderCustomAction.d.ts

@@ -1,10 +1,10 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "../Foundation/NSArray.js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { _NSProgress } from "../Foundation/NSProgress.js";
 import type { _NSString } from "../Foundation/NSString.js";
 export interface _NSFileProviderCustomAction {
     /**
      * Perform a custom action identified by `actionIdentifier`, on items identified by `itemIdentifiers`. Custom actions are defined in the File Provider Extension's Info.plist, under the `NSExtensionFileProviderActions` key. The format of this key is identical to actions defined in a FileProviderUI extension. Cancellations: ------------ If the NSProgress returned by this method is cancelled, the extension should call the completion handler with (NSUserCancelledError) in the NSProgress cancellation handler.
      */
-    performActionWithIdentifier$onItemsWithIdentifiers$completionHandler$?(actionIdentifier: _NSString, itemIdentifiers: _NSArray, completionHandler: NobjcObject | null): _NSProgress;
+    performActionWithIdentifier$onItemsWithIdentifiers$completionHandler$?(actionIdentifier: _NSString, itemIdentifiers: _NSArray, completionHandler: ((error: _NSError) => void) | null): _NSProgress;
 }

package/dist/FileProvider/NSFileProviderEnumerator.d.ts

@@ -1,4 +1,3 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSFileProviderChangeObserver } from "./NSFileProviderChangeObserver.js";
 import type { _NSFileProviderEnumerationObserver } from "./NSFileProviderEnumerationObserver.js";
 import type { _NSData } from "../Foundation/NSData.js";
@@ -15,5 +14,5 @@ export interface _NSFileProviderEnumerator {
     /**
      * Request the current sync anchor. To keep an enumeration updated, the system will typically - request the current sync anchor (1) - enumerate items starting with an initial page - continue enumerating pages, each time from the page returned in the previous enumeration, until finishEnumeratingUpToPage: is called with nextPage set to nil - enumerate changes starting from the sync anchor returned in (1), until finishEnumeratingChangesUpToSyncAnchor: is called with the latest sync anchor. If moreComing is YES, continue enumerating changes, using the latest sync anchor returned. If moreComing is NO, stop enumerating. - When the extension calls -[NSFileProviderManager signalEnumeratorForContainerItemIdentifier: completionHandler:] to signal more changes, the system will again enumerate changes, starting at the latest known sync anchor from finishEnumeratingChangesUpToSyncAnchor. NOTE that the change-based observation methods are marked optional for historical reasons, but are really required. System performance will be severely degraded if they are not implemented.
      */
-    currentSyncAnchorWithCompletionHandler$?(completionHandler: NobjcObject | null): void;
+    currentSyncAnchorWithCompletionHandler$?(completionHandler: ((currentAnchor: _NSData) => void) | null): void;
 }

package/dist/FileProvider/NSFileProviderErrorCode.d.ts

@@ -0,0 +1,27 @@
+export declare const NSFileProviderErrorCode: {
+    readonly NSFileProviderErrorNotAuthenticated: -1000;
+    readonly NSFileProviderErrorFilenameCollision: -1001;
+    readonly NSFileProviderErrorSyncAnchorExpired: -1002;
+    readonly NSFileProviderErrorPageExpired: -1002;
+    readonly NSFileProviderErrorInsufficientQuota: -1003;
+    readonly NSFileProviderErrorServerUnreachable: -1004;
+    readonly NSFileProviderErrorNoSuchItem: -1005;
+    readonly NSFileProviderErrorDeletionRejected: -1006;
+    readonly NSFileProviderErrorDirectoryNotEmpty: -1007;
+    readonly NSFileProviderErrorProviderNotFound: -2001;
+    readonly NSFileProviderErrorProviderTranslocated: -2002;
+    readonly NSFileProviderErrorOlderExtensionVersionRunning: -2003;
+    readonly NSFileProviderErrorNewerExtensionVersionFound: -2004;
+    readonly NSFileProviderErrorCannotSynchronize: -2005;
+    readonly NSFileProviderErrorNonEvictableChildren: -2006;
+    readonly NSFileProviderErrorUnsyncedEdits: -2007;
+    readonly NSFileProviderErrorNonEvictable: -2008;
+    readonly NSFileProviderErrorVersionNoLongerAvailable: -2009;
+    readonly NSFileProviderErrorExcludedFromSync: -2010;
+    readonly NSFileProviderErrorDomainDisabled: -2011;
+    readonly NSFileProviderErrorProviderDomainTemporarilyUnavailable: -2012;
+    readonly NSFileProviderErrorProviderDomainNotFound: -2013;
+    readonly NSFileProviderErrorApplicationExtensionNotFound: -2014;
+    readonly NSFileProviderErrorLocalVersionConflictingWithServer: -2015;
+};
+export type NSFileProviderErrorCode = typeof NSFileProviderErrorCode[keyof typeof NSFileProviderErrorCode];

package/dist/FileProvider/NSFileProviderErrorCode.js

@@ -0,0 +1,27 @@
+// AUTO-GENERATED by objcjs-types generator — DO NOT EDIT
+export const NSFileProviderErrorCode = {
+    NSFileProviderErrorNotAuthenticated: -1000,
+    NSFileProviderErrorFilenameCollision: -1001,
+    NSFileProviderErrorSyncAnchorExpired: -1002,
+    NSFileProviderErrorPageExpired: -1002,
+    NSFileProviderErrorInsufficientQuota: -1003,
+    NSFileProviderErrorServerUnreachable: -1004,
+    NSFileProviderErrorNoSuchItem: -1005,
+    NSFileProviderErrorDeletionRejected: -1006,
+    NSFileProviderErrorDirectoryNotEmpty: -1007,
+    NSFileProviderErrorProviderNotFound: -2001,
+    NSFileProviderErrorProviderTranslocated: -2002,
+    NSFileProviderErrorOlderExtensionVersionRunning: -2003,
+    NSFileProviderErrorNewerExtensionVersionFound: -2004,
+    NSFileProviderErrorCannotSynchronize: -2005,
+    NSFileProviderErrorNonEvictableChildren: -2006,
+    NSFileProviderErrorUnsyncedEdits: -2007,
+    NSFileProviderErrorNonEvictable: -2008,
+    NSFileProviderErrorVersionNoLongerAvailable: -2009,
+    NSFileProviderErrorExcludedFromSync: -2010,
+    NSFileProviderErrorDomainDisabled: -2011,
+    NSFileProviderErrorProviderDomainTemporarilyUnavailable: -2012,
+    NSFileProviderErrorProviderDomainNotFound: -2013,
+    NSFileProviderErrorApplicationExtensionNotFound: -2014,
+    NSFileProviderErrorLocalVersionConflictingWithServer: -2015,
+};

package/dist/FileProvider/NSFileProviderExtension.d.ts

@@ -3,6 +3,7 @@ import type { _NSArray } from "../Foundation/NSArray.js";
 import type { _NSData } from "../Foundation/NSData.js";
 import type { _NSDate } from "../Foundation/NSDate.js";
 import type { _NSDictionary } from "../Foundation/NSDictionary.js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { _NSNumber } from "../Foundation/NSNumber.js";
 import type { _NSObject } from "../Foundation/NSObject.js";
 import type { _NSProgress } from "../Foundation/NSProgress.js";
@@ -35,11 +36,11 @@ export declare class _NSFileProviderExtension extends _NSObject {
     /**
      * This method is called when a placeholder URL should be provided for the item at the given URL. The implementation of this method should call +[NSFileProviderManager writePlaceholderAtURL:withMetadata:error:] with the URL returned by +[NSFileProviderManager placeholderURLForURL:], then call the completion handler.
      */
-    providePlaceholderAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | null): void;
+    providePlaceholderAtURL$completionHandler$(url: _NSURL, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Should ensure that the actual file is in the position returned by URLForItemWithPersistentIdentifier:, then call the completion handler.
      */
-    startProvidingItemAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | null): void;
+    startProvidingItemAtURL$completionHandler$(url: _NSURL, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Called after the last claim to the file has been released. At this point, it is safe for the file provider to remove the content file. Care should be taken that the corresponding placeholder file stays behind after the content file has been deleted.
      */
@@ -56,47 +57,47 @@ export declare class _NSFileProviderExtension extends _NSObject {
     /**
      * Import a document. The file or package at fileURL should be moved on disk into the file provider's own storage, where it will later be uploaded. The completion block should be executed after the move on disk, but before the upload. Before doing any network, actually. In the completion block, importedDocumentItem should have these properties set: - itemIdentifier - parentItemIdentifier (to the value passed in to this method) - filename (to fileURL's resource value for key NSURLNameKey) - creationDate (to NSURLCreationDateKey) - contentModificationDate (to NSURLContentModificationDateKey) - contentType (to NSURLContentTypeKey) - documentSize (to NSURLTotalFileSizeKey on a flat file, or to the sum of the files sizes for a package) - capabilities [fileURL startAccessingSecurityScopedResource] needs to be called prior to accessing this security scoped URL, and stopAccessingSecurityScopedResource needs to be called when done. Note that itemIdentifier should be set with no network call. It doesn't have to be the final identifier. If the identifier changes after talking to the server then the file provider should send a delete for the temporary, local identifier immediately followed by an add with the final identifier. A reasonable way of organizing files in the file provider storage is: <file provider storage path>/<itemIdentifier>/<filename>.<extension> If the item identifier was to change, you should move the file on disk to update its path, under coordination with NSFileCoordinatorWritingForMoving. This is expected to work offline even if there might be a collision (another item with the same filename and parentItemIdentifier) only detected when later syncing up this change to the server. In that case, it is suggested that a follow up update to the item change its filename to something unique. This wouldn't be considered an error to import. If however you can tell right away, with no communication to your server, that there is a collision then this call should fail with error code NSFileProviderErrorFilenameCollision generated with this method: -[NSError (NSFileProviderError) fileProviderErrorForCollisionWithItem:]. The existing item set in this error will be used to handle the collision, and ask the user if she or he would like to replace the existing item. This takes into account the existing item's capabilities (particularly NSFileProviderItemCapabilitiesAllowsTrashing and AllowsDeleting.) Collision checks should be case insensitive even if the filesystem or file provider might allow two coexisting filenames differing only by their case. Upload errors (such as NSFileProviderErrorInsufficientQuota) should be handled with a subsequent update to the item, setting its uploadingError property. Upload errors should not prevent creating or importing a document, because they can be resolved at a later date (for example, when the user has quota again.) Other errors will be presented to the user, but are unexpected. If you want to prevent imports in a given directory, then the directory item's capacities should exclude NSFileProviderItemCapabilitiesAllowsAddingSubItems.
      */
-    importDocumentAtURL$toParentItemIdentifier$completionHandler$(fileURL: _NSURL, parentItemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    importDocumentAtURL$toParentItemIdentifier$completionHandler$(fileURL: _NSURL, parentItemIdentifier: _NSString, completionHandler: ((importedDocumentItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * Create a directory. This is expected to complete before doing any network. In the completion block, createdDirectoryItem should have these properties set: - itemIdentifier - parentItemIdentifier (to the value passed in to this method) - filename (to directoryName) - creationDate (to the current date and time) - contentType (to "public.folder" - UTTypeFolder) - childItemCount (to 0) - capabilities Errors (including collision errors) are handled as documented for the import method above. Directory creation is gated by the capabilities of the destination directory, with NSFileProviderItemCapabilitiesAllowsAddingSubItems.
      */
-    createDirectoryWithName$inParentItemIdentifier$completionHandler$(directoryName: _NSString, parentItemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    createDirectoryWithName$inParentItemIdentifier$completionHandler$(directoryName: _NSString, parentItemIdentifier: _NSString, completionHandler: ((createdDirectoryItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * Rename a document or a directory. This is expected to complete before doing any network. itemName is the full file or directory name, complete with its file extension. In the completion block, property renamedItem.filename should change to itemName. Property renamedItem.displayName should also be updated if you chose to overwrite that method. Errors (including collision errors) are handled as documented for the import method above. Renames are gated by the capabilities of the renamed item, with NSFileProviderItemCapabilitiesAllowsRenaming.
      */
-    renameItemWithIdentifier$toName$completionHandler$(itemIdentifier: _NSString, itemName: _NSString, completionHandler: NobjcObject | null): void;
+    renameItemWithIdentifier$toName$completionHandler$(itemIdentifier: _NSString, itemName: _NSString, completionHandler: ((renamedItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * Move an item to a new directory. This is expected to complete before doing any network. If newName is non null, the moved item should be renamed to newName. Errors (including collision errors) are handled as documented for the import method above. Moves are gated by the capabilities of both the moved item with NSFileProviderItemCapabilitiesAllowsReparenting, and the destination directory with NSFileProviderItemCapabilitiesAllowsAddingSubItems.
      */
-    reparentItemWithIdentifier$toParentItemWithIdentifier$newName$completionHandler$(itemIdentifier: _NSString, parentItemIdentifier: _NSString, newName: _NSString | null, completionHandler: NobjcObject | null): void;
+    reparentItemWithIdentifier$toParentItemWithIdentifier$newName$completionHandler$(itemIdentifier: _NSString, parentItemIdentifier: _NSString, newName: _NSString | null, completionHandler: ((reparentedItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * Move an item to the trash. In the completion block, property trashedItem.isTrashed should be set to YES. You should keep track of the original parentItemIdentifier of the item before it was moved to trash, so you can move the item back where it used to be in the untrash method. You could use the trashedItem.parentItemIdentifier property for that. The trashed item should continue to belong to the working set of documents cached on the device and visible offline to the user. But if it is a directory, then all of its children should be removed from the working set and the file provider extension should send deletion events to make sure that they no longer appear in the recent lists. It is also suggested that shared documents be unshared when trashed. Trash is gated by the capabilities of the trashed item with NSFileProviderItemCapabilitiesAllowsTrashing.
      */
-    trashItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    trashItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: ((trashedItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * Move an item out of the trash. If parentItemIdentifier is nil, the file provider should attempt to put the item back where it was when it was moved to the trash; otherwise it should move it to this new parent. If the item is a directory, then the file provider extension should enumerate the children and send addition events in the working set so that the documents in the now untrashed directory may be reindexed. Untrash is gated by the capabilities of the destination directory, with NSFileProviderItemCapabilitiesAllowsAddingSubItems.
      */
-    untrashItemWithIdentifier$toParentItemIdentifier$completionHandler$(itemIdentifier: _NSString, parentItemIdentifier: _NSString | null, completionHandler: NobjcObject | null): void;
+    untrashItemWithIdentifier$toParentItemIdentifier$completionHandler$(itemIdentifier: _NSString, parentItemIdentifier: _NSString | null, completionHandler: ((untrashedItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * Delete an item forever. This is called when the user deletes an item that was already in the Trash and the item should no longer appear there after this call. This call should remove the item from the working set. Delete is gated by the capabilities of the removed item with NSFileProviderItemCapabilitiesAllowsDeleting.
      */
-    deleteItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    deleteItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Mark an item as recently used, or clear its lastUsedDate if nil. This last used date is the sort key for the recent lists. It is the primary hint that an item must belong to the working set cached and indexed on the user's device. The file provider is asked to persist the new last used date on disk, then call the completion callback with the updated last used date. At a later point, the file provider should sync the new last used date to their server. The error parameter is here for debugging purposes alone; it won't be presented to the user or otherwise handled, but it will be logged.
      */
-    setLastUsedDate$forItemIdentifier$completionHandler$(lastUsedDate: _NSDate | null, itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    setLastUsedDate$forItemIdentifier$completionHandler$(lastUsedDate: _NSDate | null, itemIdentifier: _NSString, completionHandler: ((recentlyUsedItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * Tag an item, or untag it if tagData is nil. The file provider is asked to persist the new tag data on disk, then call the completion callback with the updated tagged data. At a later point, the file provider should sync the new tag data to their server. Tagged items are relevant to the user and should be in the working set even if they haven't been used recently. If set, the error will be immediately presented to the user and the item just won't be tagged. On shared items, tags should sync across the devices of any one participant but shouldn't sync across users.
      */
-    setTagData$forItemIdentifier$completionHandler$(tagData: _NSData | null, itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    setTagData$forItemIdentifier$completionHandler$(tagData: _NSData | null, itemIdentifier: _NSString, completionHandler: ((taggedItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * Mark a directory as favorite (or no longer favorite if favoriteRank is nil.) The favorite rank is used to represent the relative order of two favorite directories in the UI. It is a 64 bit unsigned integer. It needs to be synced. Favorite directories are relevant to the user and should be in the working set even if they haven't been used recently. The documents and directories in the favorite directory however don't all have to be in the working set, and don't all have to be made accessible offline. The file provider is asked to persist the new favorite rank on disk, then call the completion callback with the updated favorite rank. At a later point, the file provider should sync the new favorite rank to their server.
      */
-    setFavoriteRank$forItemIdentifier$completionHandler$(favoriteRank: _NSNumber | null, itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    setFavoriteRank$forItemIdentifier$completionHandler$(favoriteRank: _NSNumber | null, itemIdentifier: _NSString, completionHandler: ((favoriteItem: _NSFileProviderItem, error: _NSError) => void) | null): void;
     /**
      * The system calls this method to fetch thumbnails. The @p perThumbnailCompletionHandler should be called for each thumbnail, and @p completionHandler only after all the per thumbnail completion blocks. In the event of a global error, the implementation is allowed to skip calling the @p perThumbnailCompletionHandler for individual thumbnails. In that case, the @p completionHandler's error parameter would apply to all item identifiers for which @p perThumbnailCompletionHandler had not been called. If there is no thumbnail for a given item, the @p perThumbnailCompletionHandler should be called with its @p imageData and @p error parameters both set to nil. If the system decides that an in-flight thumbnail request is not needed anymore, it will call the returned @p NSProgress object's @p -cancel method, at which time the implementation should clean up any held resources. The system will cache the thumbnail for the item, and the cache will be invalidated when itemVersion.contentVersion changes.
      */
-    fetchThumbnailsForItemIdentifiers$requestedSize$perThumbnailCompletionHandler$completionHandler$(itemIdentifiers: _NSArray, size: CGSize, perThumbnailCompletionHandler: NobjcObject | null, completionHandler: NobjcObject | null): _NSProgress;
+    fetchThumbnailsForItemIdentifiers$requestedSize$perThumbnailCompletionHandler$completionHandler$(itemIdentifiers: _NSArray, size: CGSize, perThumbnailCompletionHandler: ((identifier: _NSString, imageData: _NSData, error: _NSError) => void) | null, completionHandler: ((error: _NSError) => void) | null): _NSProgress;
     /**
      * An identifier unique to this provider. When modifying the files stored in the directory returned by documentStorageURL, you should pass this identifier to your file coordinator's setPurposeIdentifier: method.
      * @deprecated NSFileProviderManager -providerIdentifier

package/dist/FileProvider/NSFileProviderExternalVolumeHandling.d.ts

@@ -1,7 +1,7 @@
-import type { NobjcObject } from "objc-js";
+import type { _NSError } from "../Foundation/NSError.js";
 export interface _NSFileProviderExternalVolumeHandling {
     /**
      * Implement this protocol on your extension's Principal Class in order for the system to ask your extension whether a domain located on an external volume should be connected. Your extension may use this method as an opportunity to check for, and setup if necessary, state to operate the extension. Such as prompting the user to login in your application. When creating domains on external drive, store state related to the domain in the `userInfo` parameter to `-[NSFileProviderDomain initWithDisplayName:userInfo:volumeURL:]`, such as the user's ID, to help your extension identify the domain when connected on other devices. This userInfo will be persisted on the external volume, and provided in the ReplicatedExtension initializer when the drive is connected to a new device. If your extension responds with an NSError, the domain will be in a disconnected state. Non-downloaded files in the domain will not be downloadable, and file edits will not be synced up. The system will display UI to inform the user. Your extension will be able to enumerate this domain in `+[NSFileProviderManager getDomainsWithCompletionHandler:]`, with the `-[NSFileProviderDomain disconnected]` property set as YES. If at a later point, the user has setup the necessary state to service requests for the disconnected external domain, your extension may call `-[NSFileProviderManager reconnectWithCompletionHandler:]`. If your extension does not implement this protocol, domains on external volumes will automatically be connected and instantiated in your extension.
      */
-    shouldConnectExternalDomainWithCompletionHandler$?(completionHandler: NobjcObject | null): void;
+    shouldConnectExternalDomainWithCompletionHandler$?(completionHandler: ((connectionError: _NSError) => void) | null): void;
 }

package/dist/FileProvider/NSFileProviderIncrementalContentFetching.d.ts

@@ -1,12 +1,13 @@
-import type { NobjcObject } from "objc-js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { _NSProgress } from "../Foundation/NSProgress.js";
 import type { _NSString } from "../Foundation/NSString.js";
 import type { _NSURL } from "../Foundation/NSURL.js";
+import type { _NSFileProviderItem } from "./NSFileProviderItem.js";
 import type { _NSFileProviderItemVersion } from "./NSFileProviderItemVersion.js";
 import type { _NSFileProviderRequest } from "./NSFileProviderRequest.js";
 export interface _NSFileProviderIncrementalContentFetching {
     /**
      * Update a previously provided item to a new version. If the system already has a version of an item and learns that a new version is available, it may call this method to update the existing version to a new version. The semantics of the requestedVersion parameter are the same as for the non-delta update method above.
      */
-    fetchContentsForItemWithIdentifier$version$usingExistingContentsAtURL$existingVersion$request$completionHandler$?(itemIdentifier: _NSString, requestedVersion: _NSFileProviderItemVersion | null, existingContents: _NSURL, existingVersion: _NSFileProviderItemVersion, request: _NSFileProviderRequest, completionHandler: NobjcObject | null): _NSProgress;
+    fetchContentsForItemWithIdentifier$version$usingExistingContentsAtURL$existingVersion$request$completionHandler$?(itemIdentifier: _NSString, requestedVersion: _NSFileProviderItemVersion | null, existingContents: _NSURL, existingVersion: _NSFileProviderItemVersion, request: _NSFileProviderRequest, completionHandler: ((fileContents: _NSURL, item: _NSFileProviderItem, error: _NSError) => void) | null): _NSProgress;
 }

package/dist/FileProvider/NSFileProviderKnownFolderSupporting.d.ts

@@ -1,8 +1,9 @@
-import type { NobjcObject } from "objc-js";
+import type { _NSFileProviderKnownFolderLocations } from "./NSFileProviderKnownFolderLocations.js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { NSFileProviderKnownFolders } from "./NSFileProviderKnownFolders.js";
 export interface _NSFileProviderKnownFolderSupporting {
     /**
      * Request suitable locations for known folders. This function is called when the user decides to switch some known folders to the current domain, outside of the `claimKnownFolders` call. The system provides a list of folders that the user decides to move to this domain, and expect in return non-nil locations for those known folders.
      */
-    getKnownFolderLocations$completionHandler$?(knownFolders: NSFileProviderKnownFolders, completionHandler: NobjcObject | null): void;
+    getKnownFolderLocations$completionHandler$?(knownFolders: NSFileProviderKnownFolders, completionHandler: ((arg0: _NSFileProviderKnownFolderLocations, arg1: _NSError) => void) | null): void;
 }

package/dist/FileProvider/NSFileProviderManager.d.ts

@@ -2,6 +2,7 @@ import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "../Foundation/NSArray.js";
 import type { _NSDictionary } from "../Foundation/NSDictionary.js";
 import type { _NSError } from "../Foundation/NSError.js";
+import type { _NSFileProviderService } from "../Foundation/NSFileProviderService.js";
 import type { _NSObject } from "../Foundation/NSObject.js";
 import type { _NSProgress } from "../Foundation/NSProgress.js";
 import type { _NSString } from "../Foundation/NSString.js";
@@ -15,6 +16,7 @@ import type { _NSFileProviderPendingSetEnumerator } from "./NSFileProviderPendin
 import type { NSRange } from "../structs/NSRange.js";
 import type { NSFileProviderServiceName } from "../Foundation/NSFileProviderServiceName.js";
 import type { NSProgressFileOperationKind } from "../Foundation/NSProgressFileOperationKind.js";
+import type { NSFileProviderDomainIdentifier } from "./NSFileProviderDomainIdentifier.js";
 import type { NSFileProviderDomainRemovalMode } from "./NSFileProviderDomainRemovalMode.js";
 import type { NSFileProviderItemFields } from "./NSFileProviderItemFields.js";
 import type { NSFileProviderKnownFolders } from "./NSFileProviderKnownFolders.js";
@@ -29,7 +31,7 @@ export declare class _NSFileProviderManager extends _NSObject {
     /**
      * Return the identifier and domain for a user visible URL. This method returns the identifier and domain of a user visible URL if applicable. Calling this method on a file which doesn't reside in your provider/domain, or which hasn't yet been assigned an identifier by the provider will return the Cocoa error NSFileNoSuchFileError.
      */
-    static getIdentifierForUserVisibleFileAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | null): void;
+    static getIdentifierForUserVisibleFileAtURL$completionHandler$(url: _NSURL, completionHandler: ((itemIdentifier: _NSString, domainIdentifier: NSFileProviderDomainIdentifier, error: _NSError) => void) | null): void;
     /**
      * Writes out a placeholder at the specified URL. The placeholder is used in place of the actual file for operations that do not require the file's actual data to be on disk: - if attributes are requested by an application via the getPromisedItemResourceValue: method on NSURL - or via a coordination with the NSFileCoordinatorReadingImmediatelyAvailableMetadataOnly flag set - to verify whether an application has access to a file Your extension should provide placeholders by implementing the providePlaceholderAtURL: method, but your application may choose to proactively write out placeholders to facilitate access to files. This is especially useful if your application wants to actively hand out a file URL, e.g. using UIActivityViewController, in which case it should ensure that either the file or a placeholder is present on disk first. The path of the placeholder is fixed and must be determined in advance by calling the placeholderURLForURL: method.
      */
@@ -41,19 +43,19 @@ export declare class _NSFileProviderManager extends _NSObject {
     /**
      * Register a domain in which items can be stored. If a domain with the same identifier already exists, `addDomain` will update the display name and hidden state of the domain and succeed. When the domain is backed by a NSFileProviderReplicatedExtension, the system will create a disk location where the domain will be replicated. If that location already exists on disk this call will fail with the code NSFileWriteFileExistsError.
      */
-    static addDomain$completionHandler$(domain: _NSFileProviderDomain, completionHandler: NobjcObject | null): void;
+    static addDomain$completionHandler$(domain: _NSFileProviderDomain, completionHandler: ((error: _NSError) => void) | null): void;
     /** Remove a domain. */
-    static removeDomain$completionHandler$(domain: _NSFileProviderDomain, completionHandler: NobjcObject | null): void;
+    static removeDomain$completionHandler$(domain: _NSFileProviderDomain, completionHandler: ((error: _NSError) => void) | null): void;
     /** Remove a domain with options */
-    static removeDomain$mode$completionHandler$(domain: _NSFileProviderDomain, mode: NSFileProviderDomainRemovalMode, completionHandler: NobjcObject | null): void;
+    static removeDomain$mode$completionHandler$(domain: _NSFileProviderDomain, mode: NSFileProviderDomainRemovalMode, completionHandler: ((_result: _NSURL, error: _NSError) => void) | null): void;
     /** Get all registered domains. */
-    static getDomainsWithCompletionHandler$(completionHandler: NobjcObject | null): void;
+    static getDomainsWithCompletionHandler$(completionHandler: ((domains: _NSArray, error: _NSError) => void) | null): void;
     /** Remove all registered domains. */
-    static removeAllDomainsWithCompletionHandler$(completionHandler: NobjcObject | null): void;
+    static removeAllDomainsWithCompletionHandler$(completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Request the creation of a new domain that will take ownership of on-disk data that were previously managed without a file provider. You can use this method in order to migrate from a software that managed a file hierarchy on disk to a NSFileProviderExtension without having to redownload the data that was already on disk. The URL is expected to point to a directory. That directory will be moved away, its ownership being taken by the system. From this point, your extension's createItemFromTemplate method will be called for every item found in the directory with the special NSFileProviderCreateItemMayAlreadyExist option. In case a domain with the same name already exists in the file provider manager, the call will fail with the code NSFileWriteFileExistsError. The URL will remain untouched. In case the system does not allow the extension to request a migration, the call will fail with NSFeatureUnsupportedError. In case of success, the URL will become invalid and the domain will be created. The completion handler is called as soon as the domain is created. Your provider will receive calls to createItemBasedOnTemplate afterward. When the import of the file hierarchy is finished, the system calls -[NSFileProviderExtension signalDidFinishImportingItemsFromDiskWithCompletionHandler:]. In case -[NSFileProviderManager reimportItemsBelowItemWithIdentifier:completionHandler:] is called before the end of the import, a single call to importDidFinishWithCompletionHandler will be received for both the import and the scan.
      */
-    static importDomain$fromDirectoryAtURL$completionHandler$(domain: _NSFileProviderDomain, url: _NSURL, completionHandler: NobjcObject | null): void;
+    static importDomain$fromDirectoryAtURL$completionHandler$(domain: _NSFileProviderDomain, url: _NSURL, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Check if a URL is eligible for storing a domain. This returns whether the check has been performed succesfully - NOT whether the drive is eligible. If an error was encountered while checking, this method returns FALSE and an error describing the problem will be set. The eligible parameter will contain the result of the check and indicate whether the volume can be used to store FP domains. Its value is only defined if the call returns YES. The url can be any existing and accessible URL on the volume for which you want to assess eligibility. The checks are volume-wide and the exact location on the volume doesn't impact them. If a drive is eligible, unsupportedReason will be empty (0). Otherwise it will contain the list of identified conditions that currently prevent this drive from being used to store FP domains.
      */
@@ -63,15 +65,15 @@ export declare class _NSFileProviderManager extends _NSObject {
     /**
      * Call this method either in the app or in the extension to trigger an enumeration, typically in response to a push. When using NSFileProviderExtension, the system will enumerate containers while the user is viewing them in the UI. If there are changes to the container while an enumerator is open, call this method with the identifier of that container. This will trigger another call to -[NSFileProviderEnumerator enumerateChangesForObserver:fromSyncAnchor:] on that enumerator, and the UI will be refreshed, giving the user live updates on the presented enumeration. If there are changes in the working set, call this method with containerItemIdentifier set to NSFileProviderWorkingSetContainerItemIdentifier, even if there is no live enumeration for the working set container. When using NSFileProviderReplicatedExtension, only call this method with NSFileProviderWorkingSetContainerItemIdentifier. Other container identifiers are ignored. The system will automatically propagate working set changes to the UI, without explicitly signaling the containers currently being viewed in the UI. In addition to using this method, your application/extension can register for pushes using the PKPushTypeFileProvider push type. Pushes of the form { "container-identifier": "<identifier>", "domain": "<domain identifier>" } with a topic of "<your application identifier>.pushkit.fileprovider" will be translated into a call to signalEnumeratorForContainerItemIdentifier:completionHandler:.
      */
-    signalEnumeratorForContainerItemIdentifier$completionHandler$(containerItemIdentifier: _NSString, completion: NobjcObject | null): void;
+    signalEnumeratorForContainerItemIdentifier$completionHandler$(containerItemIdentifier: _NSString, completion: ((error: _NSError) => void) | null): void;
     /**
      * Return the security scoped URL to the user visible location for an item identifier. The caller must use file coordination (see NSFileCoordinator) if it wishes to read the content or list the children of the URL. The caller should not try to manipulate files in the user visible location. All changes coming from the provider should go through updates in the working set that will be applied to the user visible items by the system. The location may differ from the logical parentURL/filename. If an item on disk cannot be assigned the requested name (e.g. because the local file system has different case collision rules from the provider), one of the items can be assigned a different local name. In that case, the "com.apple.fileprovider.before-bounce#PX" extended attribute will contain the filename before collision resolution. This attribute is only set if the item has been assigned a different local name following a collision. Such local names are not synced up to the provider; the purpose of the attribute is to enable consistency checkers to detect this case. Before accessing the content of the returned URL, the caller must call `-[NSURL startAccessingSecurityScopedResource] on the returned URL and call `-[NSURL stopAccessingSecurityScopedResource]` when done accessing the content. The returned URL grants read-write access to the user visible location for the corresponding item. On iOS, for replicated domains, the extension process will never be granted access to the user visible location, this function will always fail with `NSFileReadNoPermissionError`.
      */
-    getUserVisibleURLForItemIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    getUserVisibleURLForItemIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: ((userVisibleFile: _NSURL, error: _NSError) => void) | null): void;
     /**
      * Registers the given NSURLSessionTask to be responsible for the specified item. A given item can only have one task registered at a time. The task must be suspended at the time of calling. The task's progress is displayed on the item when the task is executed.
      */
-    registerURLSessionTask$forItemWithIdentifier$completionHandler$(task: _NSURLSessionTask, identifier: _NSString, completion: NobjcObject | null): void;
+    registerURLSessionTask$forItemWithIdentifier$completionHandler$(task: _NSURLSessionTask, identifier: _NSString, completion: ((error: _NSError) => void) | null): void;
     /**
      * A temporary directory suitable to store files that will be exchanged with the system. The returned URL is guaranteed to be on the same volume as the user visible URL, making sure the system can atomatically clone/move files from that location to the user visible URL. The provider can also use that directory as a target for moves and clones of content URL passed to createItemBasedOnTemplate or modifyItem. If the system cannot find a suitable directory, this calls will fail. This could happen e.g. if the domain does not exist or is in instance of initialization. This call succeeds when called from the extension process with an instance of the extension for the domain unless domain was disconnected by `-[NSFileProviderExternalVolumeHandling shouldConnectExternalDomainWithCompletionHandler:]`. It can also fail in the extension process if the domain (external) is being setup for the very first time (meaning it never existed).
      */
@@ -79,7 +81,7 @@ export declare class _NSFileProviderManager extends _NSObject {
     /**
      * Calling this method will cause the system to cancel throttling on every item which has been throttled due to the given error. This call supports the following errors: - NSFileProviderErrorNotAuthenticated - NSFileProviderErrorInsufficientQuota - NSFileProviderErrorServerUnreachable - NSFileProviderErrorCannotSynchronize - NSFileProviderErrorExcludedFromSync
      */
-    signalErrorResolved$completionHandler$(error: _NSError, completionHandler: NobjcObject | null): void;
+    signalErrorResolved$completionHandler$(error: _NSError, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Returns the global progress for the specified kind of operations This progress tracks all the ongoing kind of operations (from disk to the provider). Uploading operations are the operations from disk to the provider. Downloading operations are the operations from the provider to the disk. The global progress exposes the two following data: - Number of items with an ongoing matching kind operation along with the grand total; - Number of bytes already transferred along with the total amount of bytes to transfer. `totalUnitCount` will only be reset when there are no operations left. If new operations of the matching kind arrive while the global progress is already ongoing, they will just be summed to the existing global progress. By default, when no matching kind operations are active, the progress has its values set to 1 and its state set to finished. The progress will be updated on the main queue. It is to be retained by the caller and to be observed through KVO. The two only supported values for kind are: - NSProgressFileOperationKindUploading - NSProgressFileOperationKindDownloading The returned progress will have its fileOperationKind property set.
      */
@@ -95,29 +97,29 @@ export declare class _NSFileProviderManager extends _NSObject {
     /**
      * Notify the system that the itemIdentifiers known by the system are not valid anymore. This can be called by an extension in case it has lost track of its synchronisation state and as a consequence is not able to guarantee the stability of the itemIdentifiers anymore. In that case, the system will trigger a scan of any data that is cached on disk and call createItemBasedOnTemplate with the special NSFileProviderCreateItemMayAlreadyExist option so that the extension can specify the new itemIdentifier for those items. The provided item identifier is inclusive, meaning the specified item will be re-import as well as any children in case it is a container. In case the extension has lost its synchronisation state but is still able to guarantee the stability of the itemIdentifiers, it should make sure that querying the working set enumerator with an anchor that predates the synchronisation loss will cause a NSFileProviderErrorSyncAnchorExpired error. In case the extension has lost its synchronisation state and is not interested in preserving the data cached on disk, it can remove and re-add the affected domain. The completion handler is called as soon as the reimport is initiated and does not not reflect the end of the import. When the import of the file hierarchy is finished, the system calls -[NSFileProviderExtension importDidFinishWithCompletionHandler:]. In some circumstances, in particular in case the requested item is the root item, calling reimport will cause the system to stop the extension process. If the call is initiated from the extension, the system does not guarantee that the completion handler will be called before the extension is stopped. When called on the root item, reimport will cause the system to rebuild its backing store for the domain. See `-[NSFileProviderDomain backingStoreIdentity]`. If this method succeeds, the system will reimport at least the requested sub-tree, but may import more. If the requested item has no on-disk representation, the completion handler will be called with a NSFileProviderErrorNoSuchItem error. The same error will be reported if the reimport request happens quickly after a previous import / reimport and the corresponding item hasn't been reimported yet.
      */
-    reimportItemsBelowItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    reimportItemsBelowItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Request that the system schedules a call to -[NSFileProviderReplicatedExtension modifyItem:] for the given item identifier. The fields passed to modifyItem will contain at least the set requested via the `fields` parameter. The completion handler is called when the system has persisted the request. There is no guarantee as to when the modifyItem call will be scheduled. The completion handler may be called with an error. If the provider passes the `.content` field when the item is not downloaded, or when the item is a folder, then the system will return CocoaError(.ubiquitousFileUnavailable).
      */
-    requestModificationOfFields$forItemWithIdentifier$options$completionHandler$(fields: NSFileProviderItemFields, itemIdentifier: _NSString, options: NSFileProviderModifyItemOptions, completionHandler: NobjcObject | null): void;
+    requestModificationOfFields$forItemWithIdentifier$options$completionHandler$(fields: NSFileProviderItemFields, itemIdentifier: _NSString, options: NSFileProviderModifyItemOptions, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Request that the system remove an item from its cache. When called on a file, the file will be made dataless. When called on a directory, first each of the directory's children will be evicted (child files are made dataless, child directories are recursively evicted). Then the directory itself will be made dataless. If a non-evictable child is encountered, eviction will stop immediately and the completionHandler will be called with the NSFileProviderErrorNonEvictableChildren error. The error will include information on why and which children could not be evicted in -[NSError underlyingErrors]. The materialization state of the remaining items may be either materialized or evicted, depending on the traversal order. The completion handler is called after the items have been evicted from disk or immediately when an error occurs. Eviction might fail with the following errors : - NSFileProviderErrorDomain.NSFileProviderErrorUnsyncedEdits if the item had non-uploaded changes. - NSFileProviderErrorDomain.NSFileProviderErrorNonEvictable if the item has been marked as non-purgeable by the provider. - NSPOSIXErrorDomain.EBUSY : if the item has open file descriptors on it. - NSPOSIXErrorDomain.EMLINK : if the item has several hardlinks. - other NSPOSIXErrorDomain error codes if the system was unable to access or manipulate the corresponding file.
      */
-    evictItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    evictItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Wait for all changes on disk in the sub-hierarchy of the item to be acknowledged by the extension. This call can be used to guarantee operation ordering in a sub-hierarchy of the provider. The completion handler is called when all the changes for descendents of the item have been acknowledged by the extension. If any error is met during that process, an error will be raised, in which case the caller should not assume all the changes have been received. This call will only wait for changes affecting items that were already descendents of the requested item in the provider, or items that have been newly created on disk. It will not wait for items that are already known from the provider and are being moved in the directory. As a consequence, that call can be used from within a call to -[NSFileProviderReplicatedExtension modifyItem:baseVersion:changedFields:contents:options:completionHandler:]. Also note that the call will return immediately on items that are not directories. In case a change cannot be applied to the provider, the call will fail with NSFileProviderErrorCannotSynchronize including the NSFileProviderErrorItemKey with the identifier of the item that could not be synced if that item is known by the provider.
      */
-    waitForChangesOnItemsBelowItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    waitForChangesOnItemsBelowItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Wait for stabilization of the domain. The system will wait until it is caught up with the file system's changes up to the time of the call, then wait until it is caught up with the provider's changes up to the time of the call. The completion handler is called when both sets of changes are caught up to at least the time of the call. This is useful to enforce a consistent state for testing.
      */
-    waitForStabilizationWithCompletionHandler$(completionHandler: NobjcObject | null): void;
-    disconnectWithReason$options$completionHandler$(localizedReason: _NSString, options: NSFileProviderManagerDisconnectionOptions, completionHandler: NobjcObject | null): void;
-    reconnectWithCompletionHandler$(completionHandler: NobjcObject | null): void;
+    waitForStabilizationWithCompletionHandler$(completionHandler: ((error: _NSError) => void) | null): void;
+    disconnectWithReason$options$completionHandler$(localizedReason: _NSString, options: NSFileProviderManagerDisconnectionOptions, completionHandler: ((error: _NSError) => void) | null): void;
+    reconnectWithCompletionHandler$(completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Request that the system schedule a download for an item. The completion handler is called when the system acknowledges the download request, or with an error indicating why it didn't (e.g NSFileProviderErrorNoSuchItem.) The system will then call -fetchContentsForItemWithIdentifier at the earliest convenient time. Set rangeToMaterialize to NSMakeRange(offset, nbytes) to request a partial download. The system will then invoke -fetchPartialContentsForItemWithIdentifier instead of fetchContentsForItemWithIdentifier. For a full download, set rangeToMaterialize to NSMakeRange(NSNotFound, 0). -[NSFileProviderManager evictItemWithIdentifier:completionHandler:] must be called on a partially materialized file before requesting an extent to be downloaded from a later version of the file. This method cannot be used to download directories recursively. When invoked on a dataless directory, it will trigger an enumeration of the directory, causing a materialization of the directory one level down only. All the children of the directory will remain dataless after the enumeration.
      */
-    requestDownloadForItemWithIdentifier$requestedRange$completionHandler$(itemIdentifier: _NSString, rangeToMaterialize: NSRange, completionHandler: NobjcObject | null): void;
+    requestDownloadForItemWithIdentifier$requestedRange$completionHandler$(itemIdentifier: _NSString, rangeToMaterialize: NSRange, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * A directory suitable for storing state information for the domain. The returned URL is guaranteed to be on the same volume as the user visible URL and the temporary URL, making sure the system can atomatically clone/move files from that location to the user visible URL. The caller is responsible for managing the security scope of the returned URL. When syncing a domain on an external volume, all information about the sync state must be kept in this directory if the volume is to be shared between multiple machines. If the system cannot find a suitable directory, this call will fail. This could happen e.g. if the domain does not exist or is in instance of initialization. This call will not fail when called from the extension process with an active instance of the extension for that domain unless the domain is being setup for the very first time (meaning it never existed). Removing the domain will remove the corresponding directory along with it.
      */
@@ -125,17 +127,17 @@ export declare class _NSFileProviderManager extends _NSObject {
     /**
      * Request diagnostics collection for the item. This will prompt the user about an issue with the sync in the provider and ask their permission to collection diagnostic information and to send them to Apple for further analysis. This call is to be used wisely with care given there's global throttling on it preventing spamming the users. Furthermore it should be used in collaboration with Apple when you detect a misbehavior in the sync in your provider likely caused by a system bug and you need to work with Apple in order to resolve it. This will return whether the call was allowed or not - not if it suceed This method will only return an error if the user was not on a Seed build It is mandatory to provide an error for the item why the collection is requested. The error won't be shown to the user (a generic message will be shown instead) It will surface in the generated report though It is important to note that even if the call is allowed, it might not trigger diagnostic collection nor prompt to the user depending on the system state and other throttling parameters
      */
-    requestDiagnosticCollectionForItemWithIdentifier$errorReason$completionHandler$(itemIdentifier: _NSString, errorReason: _NSError, completionHandler: NobjcObject | null): void;
+    requestDiagnosticCollectionForItemWithIdentifier$errorReason$completionHandler$(itemIdentifier: _NSString, errorReason: _NSError, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Request the specified known folders to be synced by this domain. This method allows the provider to claim a set of known folders described by the non-null properties of the knownFolders parameter. The system will only enable sync for those folders in that domain if the set of locations is valid and if the user agrees. This API should only be called as a result of the user requesting, via UI in the provider's application, that they wish to start syncing the Desktop and Document folders. If the provider chooses to implement a UI which invokes this API, the provider should also implement a UI for the user to request to stop syncing the Desktop and Document folders, using the `-[NSFileProviderManager releaseKnownFolders:localizedReason:completionHandler:]` method. The reason specified in this call is a custom string that the provider can pass and will be presented to the user as a way to explain why it is claiming those known folders. One suggested phrasing would be: > Keep your Desktop & Documents in sync with <Provider name> and access them from other devices and from <Provider website>. If the user denies the transition of the known folders, the call will fail with `NSUserCancelledError`. The call will fail if: - one or more locations are not folders - multiple locations are backed by the same folder - a known folder doesn't live on the same volume as the root of the domain - the known folders don't have the same parent folder - ... Currently, only claiming both ~/Desktop and ~/Documents together is allowed.
      */
-    claimKnownFolders$localizedReason$completionHandler$(knownFolders: _NSFileProviderKnownFolderLocations, localizedReason: _NSString, completionHandler: NobjcObject | null): void;
+    claimKnownFolders$localizedReason$completionHandler$(knownFolders: _NSFileProviderKnownFolderLocations, localizedReason: _NSString, completionHandler: ((arg0: _NSError) => void) | null): void;
     /**
      * Request that the system stops replicating the specified known folders in the domain. This call can be used by the provider to immediately disable replication of the specified known folders.
      */
-    releaseKnownFolders$localizedReason$completionHandler$(knownFolders: NSFileProviderKnownFolders, localizedReason: _NSString, completionHandler: NobjcObject | null): void;
+    releaseKnownFolders$localizedReason$completionHandler$(knownFolders: NSFileProviderKnownFolders, localizedReason: _NSString, completionHandler: ((arg0: _NSError) => void) | null): void;
     /** Retrieve the service with the specified named for the specified item. */
-    getServiceWithName$itemIdentifier$completionHandler$(serviceName: NSFileProviderServiceName, itemIdentifier: _NSString, completionHandler: NobjcObject | null): void;
+    getServiceWithName$itemIdentifier$completionHandler$(serviceName: NSFileProviderServiceName, itemIdentifier: _NSString, completionHandler: ((_Nullable_result: _NSFileProviderService, arg1: _NSError) => void) | null): void;
     /**
      * List the available operations. This lists all of the operations that are ready to be scheduled by the system. The system waits for all the pending disk and working set updates to be known before returning. The operations that are returned may become invalid if the system receives new disk or working set events, or if some operation are scheduled using -runTestingOperations:error:.
      */

package/dist/FileProvider/NSFileProviderPartialContentFetching.d.ts

@@ -1,13 +1,16 @@
-import type { NobjcObject } from "objc-js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { _NSProgress } from "../Foundation/NSProgress.js";
 import type { _NSString } from "../Foundation/NSString.js";
+import type { _NSURL } from "../Foundation/NSURL.js";
+import type { _NSFileProviderItem } from "./NSFileProviderItem.js";
 import type { _NSFileProviderItemVersion } from "./NSFileProviderItemVersion.js";
 import type { _NSFileProviderRequest } from "./NSFileProviderRequest.js";
 import type { NSRange } from "../structs/NSRange.js";
 import type { NSFileProviderFetchContentsOptions } from "./NSFileProviderFetchContentsOptions.js";
+import type { NSFileProviderMaterializationFlags } from "./NSFileProviderMaterializationFlags.js";
 export interface _NSFileProviderPartialContentFetching {
     /**
      * Download the requested extent of an item for the given identifier and return it via the completion handler. If this protocol is not implemented the system defaults to fetchContentsForItemWithIdentifier. The requestedVersion parameter specifies which version should be returned. This version will always be specified by the system so as to prevent extents from different versions from being written into the same file. The system tolerates a version mismatch for the first materialization of a fully dataless file (strictVersion=NO). The requested range is <location , length>. The implementation can provide any properly aligned range that covers the requested range (including the entire item). The system provides the minimal alignment value. The location (or start offset) of the fetched range should be a multiple of this value for it to be considered properly aligned. The length of the fetched range should be a multiple of this value, with an exception for the end of the file, checked against the documentSize attribute the implementation supplied for this item. The alignment value should not be expected to be stable across reboots. It is guaranteed by the system to be a power of two. In addition to the content the extension needs to fill in fetchedRange with either the requestest range, <location , length>, or indicate full materialization with, < 0, file size>. On-disk layout: --------------- The retrieved content at `fileContents` URL must be a regular file on the same volume as the user-visible URL. A suitable location can be retrieved using -[NSFileProviderManager temporaryDirectoryURLWithError:]. The file contents outside of the fetched range are ignored by the system. The system only requires the file to be at least as large as the end of the fetched range. For instance, if the fetchedRange is {offset:0x100000, length:0x1000}, the file size must be at least 0x101000 bytes. Any data (or lack thereof) beyond the fetched range is ignored. The fetched range must be stored in this file at the same offset as the range indicates. For instance if the retrievedRange is {offset:0x100000, length:0x1000} then it should actually be at offset 0x100000 in the `fileContents` file. The ranges {0, 0x100000}, and {0x101000, EOF} can be anything including sparse ranges. Concurrent Downloads: --------------- The system will call fetchContents concurrently if there are multiple outstanding file download requests. The provider can control the concurrency by setting the key NSExtensionFileProviderDownloadPipelineDepth in the Info.plist of the extension to the number of concurrent downloads that the system should create per domain. This number must be between 1 and 128, inclusive. File ownership: --------------- The system clones and unlinks the received fileContents. The extension should not mutate the corresponding file after calling the completion handler. If the extension wishes to keep a copy of the content, it must provide a clone of the that content as the URL passed to the completion handler. In case the extension or the system crashes between the moment the completion handler is called and the moment the system unlinks the file, the file may unexpectedly still be on disk the next time an instance of the extension is created. The extension is then responsible for deleting that file. Disallowing processes from fetching items: --------------- The system automatically downloads files on POSIX accesses. The extension may wish to disallow this class of downloads for specific applications. The extension can set an array of strings into the UserDefault key "NSFileProviderExtensionNonMaterializingProcessNames". A process whose executable's filename on disk is an exact match for an entry in this array will not be allowed to fetch items in the extension's domains. The comparison is case sensitive. In macOS 11.0 and later, this list will be checked when a download is initiated through a POSIX filesystem call. In macOS 11.4 and later, this list will also be checked for downloads initiated through file coordination. Error cases: ------------ If the download fails because the item is unknown, the call should fail with the NSFileProviderErrorNoSuchItem error. In that case, the system will consider the item has been removed from the domain and will attempt to delete it from disk. In case that deletion fails because there are local changes on this item, the system will re-create the item using createItemBasedOnTemplate. If the user does not have access to the content of the file, the provider can fail the call with NSCocoaErrorDomain and code NSFileReadNoPermissionError. That error will then be presented to the user. The extension can also report the NSFileProviderErrorNotAuthenticated, NSFileProviderErrorServerUnreachable in case the item cannot be fetched because of the current state of the system / domain. In those cases, the system will present an appropriate error message and back off until the next time it is signalled. If the requested version cannot be retrieved, the provider can choose to provide a different version of the file, unless NSFileProviderFetchContentsOptionsStrictVersioning is set. In this case, the provider should fail with NSFileProviderErrorVersionNoLongerAvailable. If some content is returned, the item must have the corresponding version. The system will detect any mismatch and handle it as a remote update. For the reading application, the materialization will fail with the same error as reading from a dataless file that got remotely updated (-1/errno=ESTALE). Upon retry the new version will be requested by the system. Any other error will be considered to be transient and will cause the download to be retried. Cancellations: ------------ If the NSProgress returned by this method is cancelled, the extension should call the completion handler with (nil, nil, someRange, 0, NSUserCancelledError) in the NSProgress cancellation handler. The returned NSProgress is used to show progress to the user. If the user cancels the fetch, the extension should stop fetching the item, as it is no longer required. Execution time: --------------- The system will grant enough time to the extension to download the file. The system will interrupt the call if it stops making progress or if download takes an unexpectedly long time. In that case, the system will call `cancel` on the progress. The extension is then expected to quickly call the completion handler.
      */
-    fetchPartialContentsForItemWithIdentifier$version$request$minimalRange$aligningTo$options$completionHandler$?(itemIdentifier: _NSString, requestedVersion: _NSFileProviderItemVersion, request: _NSFileProviderRequest, requestedRange: NSRange, alignment: number, options: NSFileProviderFetchContentsOptions, completionHandler: NobjcObject | null): _NSProgress;
+    fetchPartialContentsForItemWithIdentifier$version$request$minimalRange$aligningTo$options$completionHandler$?(itemIdentifier: _NSString, requestedVersion: _NSFileProviderItemVersion, request: _NSFileProviderRequest, requestedRange: NSRange, alignment: number, options: NSFileProviderFetchContentsOptions, completionHandler: ((fileContents: _NSURL, item: _NSFileProviderItem, retrievedRange: NSRange, flags: NSFileProviderMaterializationFlags, error: _NSError) => void) | null): _NSProgress;
 }