objcjs-types 0.1.0 → 0.2.0

package/dist/FSKit/FSVolumeOperations.d.ts

@@ -15,7 +15,7 @@ export interface _FSVolumeOperations extends _FSVolumePathConfOperations {
     /**
      * Mounts this volume, using the specified options. FSKit calls this method as a signal that some process is trying to mount this volume. Your file system receives a call to ``activate(options:replyHandler:)`` prior to receiving any mount calls. - Parameters: - options: Options to apply to the mount. These can include security-scoped file paths. There are no defined options currently. - reply: A block or closure to indicate success or failure. If mounting fails, pass an error as the one parameter to the reply handler. If mounting succeeds, pass `nil`. For an `async` Swift implementation, there's no reply handler; simply return normally.
      */
-    mountWithOptions$replyHandler$?(options: _FSTaskOptions, reply: NobjcObject): void;
+    mountWithOptions$replyHandler$?(options: _FSTaskOptions, reply: NobjcObject | null): void;
     /**
      * Unmounts this volume. Clear and flush all cached state in your implementation of this method. - Parameters: - reply: A block or closure to indicate success or failure. If unmounting fails, pass an error as the one parameter to the reply handler. If unmounting succeeds, pass `nil`. For an `async` Swift implementation, there's no reply handler; simply return normally.
      */
@@ -23,59 +23,59 @@ export interface _FSVolumeOperations extends _FSVolumePathConfOperations {
     /**
      * Synchronizes the volume with its underlying resource. After calling this method, FSKit assumes that the volume has sent all pending I/O or metadata to its resource. - Parameters: - flags: Timing flags, as defined in `mount.h.` These flags let the file system know whether to run the operation in a blocking or nonblocking fashion. - reply: A block or closure to indicate success or failure. If synchronization fails, pass an error as the one parameter to the reply handler. If synchronization succeeds, pass `nil`. For an `async` Swift implementation, there's no reply handler; simply throw an error or return normally.
      */
-    synchronizeWithFlags$replyHandler$?(flags: FSSyncFlags, reply: NobjcObject): void;
+    synchronizeWithFlags$replyHandler$?(flags: FSSyncFlags, reply: NobjcObject | null): void;
     /**
      * Fetches attributes for the given item. For file systems that don't support hard links, set ``FSItemAttributes/linkCount`` to `1` for regular files and symbolic links. If the item's `bsdFlags` contain the `UF_COMPRESSED` flag, your file system returns the uncompressed size of the file. - Parameters: - desiredAttributes: A requested set of attributes to get. The implementation inspects the request's ``FSItemGetAttributesRequest/wantedAttributes`` to determine which attributes to populate. - item: The item to get attributes for. - reply: A block or closure to indicate success or failure. If getting attributes succeeds, pass an ``FSItemAttributes`` with the requested attributes populated and a `nil` error. If getting attributes fails, pass the relevant error as the second parameter; FSKit ignores any ``FSItemAttributes`` in this case. For an `async` Swift implementation, there's no reply handler; simply return the ``FSItemAttributes`` or throw an error.
      */
-    getAttributes$ofItem$replyHandler$?(desiredAttributes: _FSItemGetAttributesRequest, item: _FSItem, reply: NobjcObject): void;
+    getAttributes$ofItem$replyHandler$?(desiredAttributes: _FSItemGetAttributesRequest, item: _FSItem, reply: NobjcObject | null): void;
     /**
      * Sets the given attributes on an item. Several attributes are considered "read-only", and an attempt to set these attributes results in an error with the code `EINVAL`. A request may set ``FSItem/Attributes/size`` beyond the end of the file. If the underlying file system doesn't support sparse files, allocate space to fill the new file size. Either fill this space with zeroes, or configure it to read as zeroes. If a request sets the file size below the current end-of-file, truncate the file and return any unused space to the file system as free space. Ignore attempts to set the size of directories or symbolic links; don't produce an error. If the caller attepts to sest an attribute not supported by the on-disk file system format, don't produce an error. The upper layers of the framework will detect this situation. - Parameters: - newAttributes: A request containing the attributes to set. - item: The item on which to set the attributes. - reply: A block or closure to indicate success or failure. If setting attributes succeeds, pass an ``FSItemAttributes`` with the item's updated attributes and a `nil` error. If setting attributes fails, pass the relevant error as the second parameter; FSKit ignores any ``FSItemAttributes`` in this case. For an `async` Swift implementation, there's no reply handler; simply return the ``FSItemAttributes`` or throw an error.
      */
-    setAttributes$onItem$replyHandler$?(newAttributes: _FSItemSetAttributesRequest, item: _FSItem, reply: NobjcObject): void;
+    setAttributes$onItem$replyHandler$?(newAttributes: _FSItemSetAttributesRequest, item: _FSItem, reply: NobjcObject | null): void;
     /**
      * Looks up an item within a directory. If no item matching `name` exists in the directory indicated by `directory`, complete the request with an error with a domain of <doc://com.apple.documentation/documentation/Foundation/NSPOSIXErrorDomain> and a code of `ENOENT`. > Tip: The ``FSFileName`` sent back to the caller may differ from the `name` parameter. This flexibility allows your implementation to handle case-insensitive and case-sensitive file systems. It might also be the case that `name` uses a composed Unicode string, but the name maintained by the file system and provided to the caller is uncomposed Unicode. - Parameters: - name: The name of the item to look up. - directory: The directory in which to look up the item. - reply: A block or closure to indicate success or failure. If lookup succeeds, pass the found ``FSItem`` and its ``FSFileName`` (as saved within the file system), along with a `nil` error. If lookup fails, pass the relevant error as the third parameter; any ``FSItem`` or ``FSFileName`` are ignored in this case. For an `async` Swift implementation, there's no reply handler; simply return the ``FSItem`` and ``FSFileName`` as a tuple or throw an error.
      */
-    lookupItemNamed$inDirectory$replyHandler$?(name: _FSFileName, directory: _FSItem, reply: NobjcObject): void;
+    lookupItemNamed$inDirectory$replyHandler$?(name: _FSFileName, directory: _FSItem, reply: NobjcObject | null): void;
     /**
      * Reclaims an item, releasing any resources allocated for the item. FSKit guarantees that for every ``FSItem`` returned by the volume, a corresponding reclaim operation occurs after the upper layers no longer reference that item. > Note: Block device file systems may assess whether an underyling resource terminates before processing reclaim operations. On unary file systems, for example, the associated volumes unmount when such resources disconnect from the system. The unmount triggers a reclaiming of all items. Some implementations benefit greatly from short-circuiting in such cases. With a terminated resource, all I/O results in an error, making short-circuiting the most efficient response. - Parameters: - item: The item to reclaim. - reply: A block or closure to indicate success or failure. If removal fails, pass an error as the one parameter to the reply handler. If removal succeeds, pass `nil`. For an `async` Swift implementation, there's no reply handler; simply throw an error or return normally.
      */
-    reclaimItem$replyHandler$?(item: _FSItem, reply: NobjcObject): void;
+    reclaimItem$replyHandler$?(item: _FSItem, reply: NobjcObject | null): void;
     /**
      * Reads a symbolic link. - Parameters: - item: The symbolic link to read from. FSKit guarantees this item is of type ``FSItem/ItemType/symlink``. - reply: A block or closure to indicate success or failure. If reading succeeds, pass the link's contents as an ``FSFileName`` and a `nil` error. If reading fails, pass the relevant error as the second parameter; FSKit ignores any ``FSFileName`` in this case. For an `async` Swift implementation, there's no reply handler; simply return the ``FSFileName`` or throw an error.
      */
-    readSymbolicLink$replyHandler$?(item: _FSItem, reply: NobjcObject): void;
+    readSymbolicLink$replyHandler$?(item: _FSItem, reply: NobjcObject | null): void;
     /**
      * Creates a new file or directory item. If an item named `name` already exists in the directory indicated by `directory`, complete the request with an error with a domain of <doc://com.apple.documentation/documentation/Foundation/NSPOSIXErrorDomain> and a code of `EEXIST`. - Parameters: - name: The new item's name. - type: The new item's type. Valid values are ``FSItem/ItemType/file`` or ``FSItem/ItemType/directory``. - directory: The directory in which to create the item. - newAttributes: Attributes to apply to the new item. - reply: A block or closure to indicate success or failure. If creation succeeds, pass the newly-created ``FSItem`` and its ``FSFileName``, along with a `nil` error. If creation fails, pass the relevant error as the third parameter; FSKit ignores any ``FSItem`` or ``FSFileName`` in this case. For an `async` Swift implementation, there's no reply handler; simply return a tuple of the ``FSItem`` and its ``FSFileName`` or throw an error.
      */
-    createItemNamed$type$inDirectory$attributes$replyHandler$?(name: _FSFileName, type: FSItemType, directory: _FSItem, newAttributes: _FSItemSetAttributesRequest, reply: NobjcObject): void;
+    createItemNamed$type$inDirectory$attributes$replyHandler$?(name: _FSFileName, type: FSItemType, directory: _FSItem, newAttributes: _FSItemSetAttributesRequest, reply: NobjcObject | null): void;
     /**
      * Creates a new symbolic link. If an item named `name` already exists in the directory indicated by `directory`, complete the request with an error with a domain of <doc://com.apple.documentation/documentation/Foundation/NSPOSIXErrorDomain> and a code of `EEXIST`. - Parameters: - name: The new item's name. - directory: The directory in which to create the item. - newAttributes: Attributes to apply to the new item. - contents: The contents of the new symbolic link. - reply: A block or closure to indicate success or failure. If creation succeeds, pass the newly-created ``FSItem`` and a `nil` error. If creation fails, pass the relevant error as the second parameter; FSKit ignores any ``FSItem`` in this case. For an `async` Swift implementation, there's no reply handler; simply return the ``FSItem`` or throw an error.
      */
-    createSymbolicLinkNamed$inDirectory$attributes$linkContents$replyHandler$?(name: _FSFileName, directory: _FSItem, newAttributes: _FSItemSetAttributesRequest, contents: _FSFileName, reply: NobjcObject): void;
+    createSymbolicLinkNamed$inDirectory$attributes$linkContents$replyHandler$?(name: _FSFileName, directory: _FSItem, newAttributes: _FSItemSetAttributesRequest, contents: _FSFileName, reply: NobjcObject | null): void;
     /**
      * Creates a new hard link. If creating the link fails, complete the request with an error with a domain of <doc://com.apple.documentation/documentation/Foundation/NSPOSIXErrorDomain> and the following error codes: * `EEXIST` if there's already an item named `name` in the directory. * `EMLINK` if creating the link would exceed the maximum number of hard links supported on `item`. * `ENOTSUP` if the file system doesn't support creating hard links to the type of file system object that `item` represents. - Parameters: - item: The existing item to which to link. - name: The name for the new link. - directory: The directory in which to create the link. - reply: A block or closure to indicate success or failure. If creation succeeds, pass an ``FSFileName`` of the newly-created link and a `nil` error. If creation fails, pass the relevant error as the second parameter; FSKit ignores any ``FSFileName`` in this case. For an `async` Swift implementation, there's no reply handler; simply return the ``FSFileName`` or throw an error.
      */
-    createLinkToItem$named$inDirectory$replyHandler$?(item: _FSItem, name: _FSFileName, directory: _FSItem, reply: NobjcObject): void;
+    createLinkToItem$named$inDirectory$replyHandler$?(item: _FSItem, name: _FSFileName, directory: _FSItem, reply: NobjcObject | null): void;
     /**
      * Removes an existing item from a given directory. Don't actually remove the item object itself in your implementation; instead, only remove the given item name from the given directory. Remove and deallocate the item in ``reclaimItem(_:replyHandler:)``. - Parameters: - item: The item to remove. - name: The name of the item to remove. - directory: The directory from which to remove the item. - reply: A block or closure to indicate success or failure. If removal fails, pass an error as the one parameter to the reply handler. If removal succeeds, pass `nil`. For an `async` Swift implementation, there's no reply handler; simply throw an error or return normally.
      */
-    removeItem$named$fromDirectory$replyHandler$?(item: _FSItem, name: _FSFileName, directory: _FSItem, reply: NobjcObject): void;
+    removeItem$named$fromDirectory$replyHandler$?(item: _FSItem, name: _FSFileName, directory: _FSItem, reply: NobjcObject | null): void;
     /**
      * Renames an item from one path in the file system to another. Implement renaming along the lines of this algorithm: - If `item` is a file: - If the destination file exists: - Remove the destination file. - If the source and destination directories are the same: - Rewrite the name in the existing directory. - Else: - Write the new entry in the destination directory. - Clear the old directory entry. - If `item` is a directory: - If the destination directory exists: - If the destination directory isn't empty: - Fail the operation with an error of <doc://com.apple.documentation/documentation/Foundation/NSPOSIXErrorDomain> and a code of `ENOTEMPTY`. - Else: - Remove the destination directory. - If the source and destination directories are the same: - Rewrite the name in the existing directory. - Else: - If the destination is a child of the source directory: - Fail the operation with an error. - Else: - Write the new entry in the destination directory. - Update `"."` and `".."` in the moved directory. - Clear the old directory entry. - Parameters: - item: The file system object being renamed. - sourceDirectory: The directory that currently contains the item to rename. - sourceName: The name of the item within the source directory. - destinationName: The new name of the item as it appears in `destinationDirectory`. - destinationDirectory: The directory to contain the renamed object, which may be the same as `sourceDirectory`. - overItem: The file system object if the destination exists, as discovered in a prior lookup. If this parameter is non-`nil`, mark `overItem` as deleted, so the file system can free its allocated space on the next call to ``reclaimItem(_:replyHandler:)``. After doing so, ensure the operation finishes without errors. - reply: A block or closure to indicate success or failure. If renaming succeeds, pass the ``FSFileName`` as it exists within `destinationDirectory` and a `nil` error. If renaming fails, pass the relevant error as the second parameter; FSKit ignores any ``FSFileName`` in this case. For an `async` Swift implementation, there's no reply handler; simply return the ``FSFileName`` or throw an error.
      */
-    renameItem$inDirectory$named$toNewName$inDirectory$overItem$replyHandler$?(item: _FSItem, sourceDirectory: _FSItem, sourceName: _FSFileName, destinationName: _FSFileName, destinationDirectory: _FSItem, overItem: _FSItem | null, reply: NobjcObject): void;
+    renameItem$inDirectory$named$toNewName$inDirectory$overItem$replyHandler$?(item: _FSItem, sourceDirectory: _FSItem, sourceName: _FSFileName, destinationName: _FSFileName, destinationDirectory: _FSItem, overItem: _FSItem | null, reply: NobjcObject | null): void;
     /**
      * Enumerates the contents of the given directory. This method uses the ``FSDirectoryEntryPacker/packEntry(name:itemType:itemID:nextCookie:attributes:)`` method of the `packer` parameter to deliver the enumerated items to the caller. The general flow of an enumeration implementation follows these steps: 1. Enumeration starts with a call to `enumerateDirectory` using the initial next-cookie and verifier values ``FSDirectoryCookieInitial`` and ``FSDirectoryVerifierInitial``, respectively. 2. The implementation uses `packer` to pack the initial set of directory entries. Packing also sets a `nextCookie` to use on the next call. 3. The implementation replies with a new verifier value, a nonzero value that reflects the directory's current version. 4. On the next call the implementation packs the next set of entries, starting with the item indicated by `cookie`. If `cookie` doesn't resolve to a valid directory entry, complete the request with an error of domain <doc://com.apple.documentation/documentation/Foundation/NSPOSIXErrorDomain> and code ``FSError/Code/invalidDirectoryCookie``. When packing, make sure to use acceptable directory entry names and unambiguous input to all file operations that take names without additional normalization, such as`lookupName`. > Tip: If the `attributes` parameter is `nil`, include at least two entries in a directory: `"."` and `".."`, which represent the current and parent directories, respectively. Both of these items have type ``FSItem/ItemType/directory``. For the root directory, `"."` and `".."` have identical contents. Don't pack `"."` and `".."` if `attributes` isn't `nil`. - Parameters: - directory: The item to enumerate. FSKit guarantees this item is of type ``FSItem/ItemType/directory``. - cookie: A value that indicates the location within the directory from which to enumerate. Your implementation defines the semantics of the cookie values; they're opaque to FSKit. The first call to the enumerate method passes ``FSDirectoryCookieInitial`` for this parameter. Subsequent calls pass whatever cookie value you previously passed to the packer's `nextCookie` parmeter. - verifier: A tool to detect whether the directory contents changed since the last call to `enumerateDirectory`. Your implementation defines the semantics of the verifier values; they're opaque to FSKit. The first call to the enumerate method passes ``FSDirectoryVerifierInitial`` for this parameter. Subsequent calls pass whatever cookie value you previously passed to the packer's `currentVerifier` parmeter. - attributes: The desired attributes to provide, or `nil` if the caller doesn't require attributes. - packer: An object that your implementation uses to enumerate directory items, packing one item per callback to `enumerateDirectory`. - reply: A block or closure to indicate success or failure. If enumeration succeeds, pass the current verifier and a `nil` error. If enumeration fails, pass the relevant error as the second parameter; FSKit ignores any verifier in this case. For an `async` Swift implementation, there's no reply handler; simply return the current verifier or throw an error.
      */
-    enumerateDirectory$startingAtCookie$verifier$providingAttributes$usingPacker$replyHandler$?(directory: _FSItem, cookie: NobjcObject, verifier: NobjcObject, attributes: _FSItemGetAttributesRequest | null, packer: _FSDirectoryEntryPacker, reply: NobjcObject): void;
+    enumerateDirectory$startingAtCookie$verifier$providingAttributes$usingPacker$replyHandler$?(directory: _FSItem, cookie: number, verifier: number, attributes: _FSItemGetAttributesRequest | null, packer: _FSDirectoryEntryPacker, reply: NobjcObject | null): void;
     /**
      * Activates the volume using the specified options. When FSKit calls this method, allocate any in-memory state required to represent the file system. Also allocate an ``FSItem`` for the root directory of the file system, and pass it to the reply block. FSKit caches this root item for the lifetime of the volume, and uses it as a starting point for all file look-ups. Volume activation occurs prior to any call to mount the volume. - Parameters: - options: Options to apply to the activation. These can include security-scoped file paths. There are no defined options currently. - reply: A block or closure to indicate success or failure. If activation succeeds, pass the root ``FSItem`` and a `nil` error. If activation fails, pass the relevant error as the second parameter; FSKit ignores any ``FSItem`` in this case. In Swift, `reply` takes only the ``FSItem`` as the parameter; you signal any error with a `throw`. For an `async` Swift implementation, there's no reply handler; simply return the ``FSItem`` or throw an error.
      */
-    activateWithOptions$replyHandler$?(options: _FSTaskOptions, reply: NobjcObject): void;
+    activateWithOptions$replyHandler$?(options: _FSTaskOptions, reply: NobjcObject | null): void;
     /**
      * Tears down a previously initialized volume instance. Set up your implementation to release any resources allocated for the volume instance. By the time you receive this callback, FSKit has already performed a reclaim call to release all other file nodes associated with this file system instance. Avoid performing any I/O in this method. Prior to calling this method, FSKit has already issued a sync call to perform any cleanup-related I/O. FSKit unmounts any mounted volume with a call to ``unmount(replyHandler:)`` prior to the deactivate callback. - Parameters: - options: Options to apply to the deactivation. - reply: A block or closure to indicate success or failure. If activation fails, pass an error as the one parameter to the reply handler. If activation succeeds, pass `nil`. For an `async` Swift implementation, there's no reply handler; simply throw an error or return normally.
      */
-    deactivateWithOptions$replyHandler$?(options: FSDeactivateOptions, reply: NobjcObject): void;
+    deactivateWithOptions$replyHandler$?(options: FSDeactivateOptions, reply: NobjcObject | null): void;
     /** A property that provides the supported capabilities of the volume. */
     supportedVolumeCapabilities?(): _FSVolumeSupportedCapabilities;
     /** A property that provides up-to-date statistics of the volume. */

package/dist/FSKit/FSVolumePreallocateOperations.d.ts

@@ -5,7 +5,7 @@ export interface _FSVolumePreallocateOperations {
     /**
      * Prealocates disk space for the given item. - Parameters: - item: The item for which to preallocate space. - offset: The offset from which to allocate. - length: The length of the space in bytes. - flags: Flags that affect the preallocation behavior. - reply: A block or closure to indicate success or failure. If preallocation succeeds, pass the amount of bytes allocated and a `nil` error. If preallocation fails, pass the relevant error as the second parameter; FSKit ignores any byte count in this case. For an `async` Swift implementation, there's no reply handler; simply return the allocated byte count or throw an error.
      */
-    preallocateSpaceForItem$atOffset$length$flags$replyHandler$?(item: _FSItem, offset: NobjcObject, length: number, flags: FSPreallocateFlags, reply: NobjcObject): void;
+    preallocateSpaceForItem$atOffset$length$flags$replyHandler$?(item: _FSItem, offset: NobjcObject, length: number, flags: FSPreallocateFlags, reply: NobjcObject | 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/FSVolumeReadWriteOperations.d.ts

@@ -6,9 +6,9 @@ export interface _FSVolumeReadWriteOperations {
     /**
      * Reads the contents of the given file item. If the number of bytes requested exceeds the number of bytes available before the end of the file, then the call copies only those bytes to `buffer`. If `offset` points past the last valid byte of the file, don't reply with an error but set `actuallyRead` to `0`. - Parameters: - item: The item from which to read. FSKit guarantees this item will be of type ``FSItem/ItemType/file``. - offset: The offset in the file from which to start reading. - length: The number of bytes to read. - buffer: A buffer to receive the bytes read from the file. - reply: A block or closure to indicate success or failure. If reading succeeds, pass the number of bytes read and a `nil` error. If reading fails, pass the number of bytes read prior to the error along with the relevant error. For an `async` Swift implementation, there's no reply handler; simply return the byte count or throw an error.
      */
-    readFromFile$offset$length$intoBuffer$replyHandler$?(item: _FSItem, offset: NobjcObject, length: number, buffer: _FSMutableFileDataBuffer, reply: NobjcObject): void;
+    readFromFile$offset$length$intoBuffer$replyHandler$?(item: _FSItem, offset: NobjcObject, length: number, buffer: _FSMutableFileDataBuffer, reply: NobjcObject | null): void;
     /**
      * Writes contents to the given file item. FSKit expects this routine to allocate space in the file system to extend the file as necessary. If the volume experiences an out-of-space condition, reply with an error of domain <doc://com.apple.documentation/documentation/Foundation/NSPOSIXErrorDomain> and code `ENOSPC`. - Parameters: - contents: A buffer containing the data to write to the file. - item: The item to which to write. FSKit guarantees this item will be of type ``FSItem/ItemType/file``. - offset: The offset in the file from which to start writing. - reply: A block or closure to indicate success or failure. If writing succeeds, pass the number of bytes written and a `nil` error. If writing fails, pass the number of bytes written prior to the error along with the relevant error. For an `async` Swift implementation, there's no reply handler; simply return the byte count or throw an error.
      */
-    writeContents$toFile$atOffset$replyHandler$?(contents: _NSData, item: _FSItem, offset: NobjcObject, reply: NobjcObject): void;
+    writeContents$toFile$atOffset$replyHandler$?(contents: _NSData, item: _FSItem, offset: NobjcObject, reply: NobjcObject | null): void;
 }

package/dist/FSKit/FSVolumeRenameOperations.d.ts

@@ -4,7 +4,7 @@ export interface _FSVolumeRenameOperations {
     /**
      * Sets a new name for the volume. - Parameters: - name: The new volume name. - reply: A block or closure to indicate success or failure. If renaming succeeds, pass an ``FSFileName`` of the new volume name and a `nil` error. If renaming fails, pass the relevant error as the second parameter; FSKit ignores any ``FSFileName`` in this case. For an `async` Swift implementation, there's no reply handler; simply return the ``FSFileName`` or throw an error.
      */
-    setVolumeName$replyHandler$?(name: _FSFileName, reply: NobjcObject): void;
+    setVolumeName$replyHandler$?(name: _FSFileName, reply: NobjcObject | 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/FSVolumeSupportedCapabilities.d.ts

@@ -1,4 +1,5 @@
 import type { _NSObject } from "../Foundation/NSObject.js";
+import type { _NSSecureCoding } from "../Foundation/NSSecureCoding.js";
 import type { FSVolumeCaseFormat } from "./FSVolumeCaseFormat.js";
 export declare class _FSVolumeSupportedCapabilities extends _NSObject {
     static alloc(): _FSVolumeSupportedCapabilities;
@@ -99,3 +100,5 @@ export declare class _FSVolumeSupportedCapabilities extends _NSObject {
     caseFormat(): FSVolumeCaseFormat;
     setCaseFormat$(value: FSVolumeCaseFormat): void;
 }
+export interface _FSVolumeSupportedCapabilities extends _NSSecureCoding {
+}

package/dist/FSKit/FSVolumeXattrOperations.d.ts

@@ -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): void;
+    getXattrNamed$ofItem$replyHandler$?(name: _FSFileName, item: _FSItem, reply: NobjcObject | 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): void;
+    setXattrNamed$toData$onItem$policy$replyHandler$?(name: _FSFileName, value: _NSData | null, item: _FSItem, policy: FSSetXattrPolicy, reply: NobjcObject | 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): void;
+    listXattrsOfItem$replyHandler$?(item: _FSItem, reply: NobjcObject | 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.js

@@ -1,33 +1,34 @@
 // AUTO-GENERATED by objcjs-types generator — DO NOT EDIT
 import { NobjcLibrary } from "objc-js";
+import { _bindClass } from "../bind.js";
 export const FSKit = new NobjcLibrary("/System/Library/Frameworks/FSKit.framework/FSKit");
-export const FSBlockDeviceResource = FSKit["FSBlockDeviceResource"];
-export const FSClient = FSKit["FSClient"];
-export const FSContainerIdentifier = FSKit["FSContainerIdentifier"];
-export const FSContainerStatus = FSKit["FSContainerStatus"];
-export const FSDirectoryEntryPacker = FSKit["FSDirectoryEntryPacker"];
-export const FSEntityIdentifier = FSKit["FSEntityIdentifier"];
-export const FSExtentPacker = FSKit["FSExtentPacker"];
-export const FSFileName = FSKit["FSFileName"];
-export const FSFileSystem = FSKit["FSFileSystem"];
-export const FSGenericURLResource = FSKit["FSGenericURLResource"];
-export const FSItem = FSKit["FSItem"];
-export const FSItemAttributes = FSKit["FSItemAttributes"];
-export const FSItemGetAttributesRequest = FSKit["FSItemGetAttributesRequest"];
-export const FSItemSetAttributesRequest = FSKit["FSItemSetAttributesRequest"];
-export const FSMetadataRange = FSKit["FSMetadataRange"];
-export const FSModuleIdentity = FSKit["FSModuleIdentity"];
-export const FSMutableFileDataBuffer = FSKit["FSMutableFileDataBuffer"];
-export const FSPathURLResource = FSKit["FSPathURLResource"];
-export const FSProbeResult = FSKit["FSProbeResult"];
-export const FSResource = FSKit["FSResource"];
-export const FSStatFSResult = FSKit["FSStatFSResult"];
-export const FSTask = FSKit["FSTask"];
-export const FSTaskOptions = FSKit["FSTaskOptions"];
-export const FSUnaryFileSystem = FSKit["FSUnaryFileSystem"];
-export const FSVolume = FSKit["FSVolume"];
-export const FSVolumeIdentifier = FSKit["FSVolumeIdentifier"];
-export const FSVolumeSupportedCapabilities = FSKit["FSVolumeSupportedCapabilities"];
+export const FSBlockDeviceResource = _bindClass(FSKit, "FSBlockDeviceResource");
+export const FSClient = _bindClass(FSKit, "FSClient");
+export const FSContainerIdentifier = _bindClass(FSKit, "FSContainerIdentifier");
+export const FSContainerStatus = _bindClass(FSKit, "FSContainerStatus");
+export const FSDirectoryEntryPacker = _bindClass(FSKit, "FSDirectoryEntryPacker");
+export const FSEntityIdentifier = _bindClass(FSKit, "FSEntityIdentifier");
+export const FSExtentPacker = _bindClass(FSKit, "FSExtentPacker");
+export const FSFileName = _bindClass(FSKit, "FSFileName");
+export const FSFileSystem = _bindClass(FSKit, "FSFileSystem");
+export const FSGenericURLResource = _bindClass(FSKit, "FSGenericURLResource");
+export const FSItem = _bindClass(FSKit, "FSItem");
+export const FSItemAttributes = _bindClass(FSKit, "FSItemAttributes");
+export const FSItemGetAttributesRequest = _bindClass(FSKit, "FSItemGetAttributesRequest");
+export const FSItemSetAttributesRequest = _bindClass(FSKit, "FSItemSetAttributesRequest");
+export const FSMetadataRange = _bindClass(FSKit, "FSMetadataRange");
+export const FSModuleIdentity = _bindClass(FSKit, "FSModuleIdentity");
+export const FSMutableFileDataBuffer = _bindClass(FSKit, "FSMutableFileDataBuffer");
+export const FSPathURLResource = _bindClass(FSKit, "FSPathURLResource");
+export const FSProbeResult = _bindClass(FSKit, "FSProbeResult");
+export const FSResource = _bindClass(FSKit, "FSResource");
+export const FSStatFSResult = _bindClass(FSKit, "FSStatFSResult");
+export const FSTask = _bindClass(FSKit, "FSTask");
+export const FSTaskOptions = _bindClass(FSKit, "FSTaskOptions");
+export const FSUnaryFileSystem = _bindClass(FSKit, "FSUnaryFileSystem");
+export const FSVolume = _bindClass(FSKit, "FSVolume");
+export const FSVolumeIdentifier = _bindClass(FSKit, "FSVolumeIdentifier");
+export const FSVolumeSupportedCapabilities = _bindClass(FSKit, "FSVolumeSupportedCapabilities");
 export { FSAccessMask } from "./FSAccessMask.js";
 export { FSBlockmapFlags } from "./FSBlockmapFlags.js";
 export { FSCompleteIOFlags } from "./FSCompleteIOFlags.js";

package/dist/FileProvider/NSFileProviderChangeObserver.d.ts

@@ -1,15 +1,15 @@
-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";
 export interface _NSFileProviderChangeObserver {
     /** Send updates to existing items, or insert new items. */
-    didUpdateItems$?(updatedItems: NobjcObject): void;
+    didUpdateItems$?(updatedItems: _NSArray): void;
     /** Delete existing items. No-op if the item was unknown. */
     didDeleteItemsWithIdentifiers$?(deletedItemIdentifiers: _NSArray): void;
     /**
      * This method is used to complete a batch of changes. Follow the advice in -[NSFileProviderChangeObserver suggestedBatchSize] to determine when to call this method. It is expected that the sync anchor passed here be different than the sync anchor that the enumeration started at, unless the client was already up to date on all the changes on the server, and didn't have any pending updates or deletions. Additionally, if the client is up to date on all the changes on the server it should set moreComing to NO. Sync anchor data is limited to 500 bytes. Setting a larger anchor has the same effect as calling finishEnumeratingWithError with an expired sync anchor error.
      */
-    finishEnumeratingChangesUpToSyncAnchor$moreComing$?(anchor: number, moreComing: boolean): void;
+    finishEnumeratingChangesUpToSyncAnchor$moreComing$?(anchor: _NSData, moreComing: boolean): void;
     /**
      * If the enumeration fails with NSFileProviderErrorSyncAnchorExpired, we will drop all cached data and start the enumeration over starting with sync anchor nil.
      */

package/dist/FileProvider/NSFileProviderCustomAction.d.ts

@@ -1,9 +1,10 @@
 import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "../Foundation/NSArray.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: number, itemIdentifiers: _NSArray, completionHandler: NobjcObject): _NSProgress;
+    performActionWithIdentifier$onItemsWithIdentifiers$completionHandler$?(actionIdentifier: _NSString, itemIdentifiers: _NSArray, completionHandler: NobjcObject | null): _NSProgress;
 }

package/dist/FileProvider/NSFileProviderDomainVersion.d.ts

@@ -1,4 +1,5 @@
 import type { _NSObject } from "../Foundation/NSObject.js";
+import type { _NSSecureCoding } from "../Foundation/NSSecureCoding.js";
 export declare class _NSFileProviderDomainVersion extends _NSObject {
     static alloc(): _NSFileProviderDomainVersion;
     static new(): _NSFileProviderDomainVersion;
@@ -10,3 +11,5 @@ export declare class _NSFileProviderDomainVersion extends _NSObject {
      */
     compare$(otherVersion: _NSFileProviderDomainVersion): number;
 }
+export interface _NSFileProviderDomainVersion extends _NSSecureCoding {
+}

package/dist/FileProvider/NSFileProviderEnumerating.d.ts

@@ -1,9 +1,10 @@
 import type { NobjcObject } from "objc-js";
 import type { _NSFileProviderEnumerator } from "./NSFileProviderEnumerator.js";
 import type { _NSFileProviderRequest } from "./NSFileProviderRequest.js";
+import type { _NSString } from "../Foundation/NSString.js";
 export interface _NSFileProviderEnumerating {
     /**
      * Create an enumerator for an item. This method is called when the user lists the content of folder it never accessed before. This can happen either when using Finder or when listing the content of the directory from a Terminal (for instance using the `ls` command line tool). The system will use the enumerator to list the children of the directory by calling -[NSFileProviderEnumerator enumerateItemsForObserver:startingAtPage:] until nil is passed to -[NSFileProviderEnumerationObserver finishEnumeratingUpToPage:]. Once this has been called, the directory and its children should be included in the working set. This is also used to subscribe to live updates for a single document. The system will keep an enumerator open in the extension on directories that are presented to the user (for instance, in Finder), and on document on which an application has a NSFilePresenter. The provider can use the existence of that enumerator as a hint that the user is actively seeing / using the item in question, and prioritize the delivery of updates on the item or its children in the working set. If returning nil, you must set the error out parameter. Working set enumerator: ----------------------- The working set enumerator is a special enumerator (NSFileProviderWorkingSetContainerItemIdentifier) the system uses to detect changes that should be synced to the disk and/or searchable in Spotlight. Because that enumerator is by definition used for change detection, the working set enumerator must implement -[NSFileProviderEnumerator enumerateChangesForObserver:fromSyncAnchor:] and -[NSFileProviderEnumerator currentSyncAnchorWithCompletionHandler:]. The system guarantees that it has a single consumer for the working set. This means there will never be two concurrent enumerations of the working set and will always do forward progress: the system will only ask for changes from the last requested sync anchor or the last returned sync anchor and the extension should be prepared for it. The expiration of the sync anchor of the working set will cause a very expensive scan of all the items known by the system. The system ingests the changes from the working set and applies the changes to the disk replicate and the spotlight index. Before ingesting the update for an item, the system will check if the enumeration of the item races against a call to createItemBasedOnTemplate, modifyItem, ... that may affect the item. If a potential race is detected, the system will call itemForItemIdentifier in order to resolve the race. If the provider exposes the key NSExtensionFileProviderAppliesChangesAtomically with value YES in its Info.plist, it is considered to apply the changes atomically, in which case the system does not need to check for potential races. Execution time: --------------- The system expects this call to complete quickly, it should build the object that will be used for enumeration and return it. The enumeration logic should happen when the system calls `-[NSFileProviderEnumerator enumerateItemsForObserver:startingAtPage:]` or `-[NSFileProviderEnumerator enumerateChangesForObserver:fromSyncAnchor:]`. Error cases: ------------ If containerItemIdentifier is NSFileProviderTrashContainerItemIdentifier and the extension does not support trashing items, then it should fail the call with the NSFeatureUnsupportedError error code from the NSCocoaErrorDomain domain. If the item requested containerItemIdentifier does not exist in the provider, the extension should fail with NSFileProviderErrorNoSuchItem. In that case, the system will consider the item has been deleted and attempt to delete the item from disk. 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 that case, the system will present an appropriate error message and back off until the next time it is signalled. Any other error, including crashes of the extension process, will be considered to be transient and will cause the enumeration to be retried. Errors must be in one of the following domains: NSCocoaErrorDomain, NSFileProviderErrorDomain. For errors which can not be represented using an existing error code in one of these domains, the extension should construct an NSError with domain NSCocoaErrorDomain and code NSXPCConnectionReplyInvalid. The extension should set the NSUnderlyingErrorKey in the NSError's userInfo to the error which could not be represented.
      */
-    enumeratorForContainerItemIdentifier$request$error$?(containerItemIdentifier: number, request: _NSFileProviderRequest, error: NobjcObject): _NSFileProviderEnumerator | null;
+    enumeratorForContainerItemIdentifier$request$error$?(containerItemIdentifier: _NSString, request: _NSFileProviderRequest, error: NobjcObject | null): _NSFileProviderEnumerator | null;
 }

package/dist/FileProvider/NSFileProviderEnumerationObserver.d.ts

@@ -1,11 +1,12 @@
-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";
 export interface _NSFileProviderEnumerationObserver {
-    didEnumerateItems$?(updatedItems: NobjcObject): void;
+    didEnumerateItems$?(updatedItems: _NSArray): void;
     /**
      * Call this method after enumerating a full page of items. If you set a non-nil nextPage, -[NSFileProviderEnumerator enumerateItemsToObserver:startingAtPage:] might be called with nextPage to enumerate more items. This is typically driven by the user scrolling a UIDocumentBrowserViewController presenting a directory containing more child items that would fit in the view. Page data is limited to 500 bytes. Setting a larger nextPage interrupts the enumeration.
      */
-    finishEnumeratingUpToPage$?(nextPage: number | null): void;
+    finishEnumeratingUpToPage$?(nextPage: _NSData | null): void;
     finishEnumeratingWithError$?(error: _NSError): void;
     /**
      * Size of the page suggested by the system for better performance. The system will set that property to the value it considers is best suited for the current enumeration. The system can enumerate a container in various cases (container presenter in the UI, file opened in an application, materialization of the folder by the system, ...). Each case has its own performance profile. By taking into account the suggested size, the enumeration will guarantee the best user experience possible. The system enforces a maximum of 100 times the suggested size.

package/dist/FileProvider/NSFileProviderEnumerator.d.ts

@@ -1,18 +1,19 @@
 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";
 export interface _NSFileProviderEnumerator {
     invalidate?(): void;
     /**
      * Enumerate items starting from the specified page, typically NSFileProviderInitialPageSortedByDate or NSFileProviderInitialPageSortedByName. Pagination allows large collections to be enumerated in multiple batches. The sort order specified in the initial page is important even if the enumeration results will actually be sorted again before display. If results are sorted correctly across pages, then the new results will be appended at the bottom of the list, probably not on screen, which is the best user experience. Otherwise results from the second page might be inserted in the results from the first page, causing bizarre animations. The page data should contain whatever information is needed to resume the enumeration after the previous page. If a file provider sends batches of 200 items to -[NSFileProviderEnumerationObserver didEnumerateItems:] for example, then successive pages might contain offsets in increments of 200. Execution time: --------------- This method is not expected to take more than a few seconds to complete the enumeration of a page of items. If the enumeration may not complete in a reasonable amount of time because, for instance, of bad network conditions, it is recommended to either report an error (for instance NSFileProviderErrorServerUnreachable) or return everything that is readily available and wait for the enumeration of the next page.
      */
-    enumerateItemsForObserver$startingAtPage$?(observer: _NSFileProviderEnumerationObserver, page: number): void;
+    enumerateItemsForObserver$startingAtPage$?(observer: _NSFileProviderEnumerationObserver, page: _NSData): void;
     /**
      * Enumerate changes starting from a sync anchor. This should enumerate /all/ changes (not restricted to a specific page) since the given sync anchor. Until the enumeration update is invalidated, a call to -[NSFileProviderManager signalEnumeratorForContainerItemIdentifier:completionHandler:] will trigger a call to enumerateFromSyncAnchor with the latest known sync anchor, giving the file provider (app or extension) a chance to notify about changes. The anchor data should contain whatever information is needed to resume enumerating changes from the previous synchronization point. A naive sync anchor might for example be the date of the last change that was sent from the server to the client, meaning that at that date, the client was in sync with all the server changes. A request to enumerate changes from that sync anchor would only return the changes that happened after that date, which are therefore changes that the client doesn't yet know about. 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. Execution time: --------------- This method is not expected to take more than a few seconds to complete the enumeration of a batch of items. If the enumeration may not complete in a reasonable amount of time because, for instance, of bad network conditions, it is recommended to either report an error (for instance NSFileProviderErrorServerUnreachable) or return everything that is readily available and wait for the enumeration of the next batch.
      */
-    enumerateChangesForObserver$fromSyncAnchor$?(observer: _NSFileProviderChangeObserver, syncAnchor: number): void;
+    enumerateChangesForObserver$fromSyncAnchor$?(observer: _NSFileProviderChangeObserver, syncAnchor: _NSData): void;
     /**
      * 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): void;
+    currentSyncAnchorWithCompletionHandler$?(completionHandler: NobjcObject | null): void;
 }

package/dist/FileProvider/NSFileProviderExtension.d.ts

@@ -10,6 +10,7 @@ import type { _NSString } from "../Foundation/NSString.js";
 import type { _NSURL } from "../Foundation/NSURL.js";
 import type { _NSFileProviderDomain } from "./NSFileProviderDomain.js";
 import type { _NSFileProviderEnumerator } from "./NSFileProviderEnumerator.js";
+import type { _NSFileProviderItem } from "./NSFileProviderItem.js";
 import type { CGSize } from "../structs/CGSize.js";
 export declare class _NSFileProviderExtension extends _NSObject {
     static alloc(): _NSFileProviderExtension;
@@ -19,26 +20,26 @@ export declare class _NSFileProviderExtension extends _NSObject {
      * Writes out a placeholder at the specified URL. The URL should be one returned by placeholderURLForURL:; if URL resource values are requested, the system will consult the placeholder before consulting your app extension. Metadata contains NSURLNameKey, NSURLFileSizeKey, NSURLIsPackageKey.
      * @deprecated Use the corresponding method on NSFileProviderManager instead
      */
-    static writePlaceholderAtURL$withMetadata$error$(placeholderURL: _NSURL, metadata: _NSDictionary, error: NobjcObject): boolean;
+    static writePlaceholderAtURL$withMetadata$error$(placeholderURL: _NSURL, metadata: _NSDictionary, error: NobjcObject | null): boolean;
     /**
      * Returns the designated placeholder URL for a given URL. This placeholder will be consulted before falling back to your app extension to enhance performance. To write out a placeholder, use the writePlaceHolderAtURL: method above.
      * @deprecated NSFileProviderManager +placeholderURLForURL:
      */
     static placeholderURLForURL$(url: _NSURL): _NSURL;
-    itemForIdentifier$error$(identifier: number, error: NobjcObject): number | null;
+    itemForIdentifier$error$(identifier: _NSString, error: NobjcObject | null): _NSFileProviderItem | null;
     /**
      * Should return the URL corresponding to a specific identifier. Fail if it's not a subpath of documentStorageURL. This is a static mapping; each identifier must always return a path corresponding to the same file. By default, this returns the path relative to the path returned by documentStorageURL.
      */
-    URLForItemWithPersistentIdentifier$(identifier: number): _NSURL | null;
-    persistentIdentifierForItemAtURL$(url: _NSURL): number | null;
+    URLForItemWithPersistentIdentifier$(identifier: _NSString): _NSURL | null;
+    persistentIdentifierForItemAtURL$(url: _NSURL): _NSString | null;
     /**
      * 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): void;
+    providePlaceholderAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | 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): void;
+    startProvidingItemAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | 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.
      */
@@ -50,52 +51,52 @@ export declare class _NSFileProviderExtension extends _NSObject {
     /**
      * Create an enumerator for an item. When the user opens the browse tab of the UIDocumentsBrowserViewController and selects a file provider, this is called with NSFileProviderRootContainerItemIdentifier, and -[NSFileProviderEnumerator enumerateItemsForObserver:startingAtPage:] is immediately called to list the first items available under at the root level of the file provider. As the user navigates down into directories, new enumerators are created with this method, passing in the itemIdentifier of those directories. Past enumerators are then invalidated. This method is also called with NSFileProviderWorkingSetContainerItemIdentifier, which is enumerated with -[NSFileProviderEnumerator enumerateChangesForObserver:fromSyncAnchor:]. That enumeration is special in that it isn't driven by the UIDocumentsBrowserViewController. It happens in the background to sync the working set down to the device. This is also used to subscribe to live updates for a single document. In that case, -[NSFileProviderEnumerator enumerateChangesToObserver:fromSyncAnchor:] will be called and the enumeration results shouldn't include items other than the very item that the enumeration was started on. If returning nil, you must set the error out parameter.
      */
-    enumeratorForContainerItemIdentifier$error$(containerItemIdentifier: number, error: NobjcObject): _NSFileProviderEnumerator | null;
-    supportedServiceSourcesForItemIdentifier$error$(itemIdentifier: number, error: NobjcObject): NobjcObject;
+    enumeratorForContainerItemIdentifier$error$(containerItemIdentifier: _NSString, error: NobjcObject | null): _NSFileProviderEnumerator | null;
+    supportedServiceSourcesForItemIdentifier$error$(itemIdentifier: _NSString, error: NobjcObject | null): _NSArray | null;
     /**
      * 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: number, completionHandler: NobjcObject): void;
+    importDocumentAtURL$toParentItemIdentifier$completionHandler$(fileURL: _NSURL, parentItemIdentifier: _NSString, completionHandler: NobjcObject | 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: number, completionHandler: NobjcObject): void;
+    createDirectoryWithName$inParentItemIdentifier$completionHandler$(directoryName: _NSString, parentItemIdentifier: _NSString, completionHandler: NobjcObject | 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: number, itemName: _NSString, completionHandler: NobjcObject): void;
+    renameItemWithIdentifier$toName$completionHandler$(itemIdentifier: _NSString, itemName: _NSString, completionHandler: NobjcObject | 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: number, parentItemIdentifier: number, newName: _NSString | null, completionHandler: NobjcObject): void;
+    reparentItemWithIdentifier$toParentItemWithIdentifier$newName$completionHandler$(itemIdentifier: _NSString, parentItemIdentifier: _NSString, newName: _NSString | null, completionHandler: NobjcObject | 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: number, completionHandler: NobjcObject): void;
+    trashItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: NobjcObject | 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: number, parentItemIdentifier: number | null, completionHandler: NobjcObject): void;
+    untrashItemWithIdentifier$toParentItemIdentifier$completionHandler$(itemIdentifier: _NSString, parentItemIdentifier: _NSString | null, completionHandler: NobjcObject | 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: number, completionHandler: NobjcObject): void;
+    deleteItemWithIdentifier$completionHandler$(itemIdentifier: _NSString, completionHandler: NobjcObject | 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: number, completionHandler: NobjcObject): void;
+    setLastUsedDate$forItemIdentifier$completionHandler$(lastUsedDate: _NSDate | null, itemIdentifier: _NSString, completionHandler: NobjcObject | 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: number, completionHandler: NobjcObject): void;
+    setTagData$forItemIdentifier$completionHandler$(tagData: _NSData | null, itemIdentifier: _NSString, completionHandler: NobjcObject | 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: number, completionHandler: NobjcObject): void;
+    setFavoriteRank$forItemIdentifier$completionHandler$(favoriteRank: _NSNumber | null, itemIdentifier: _NSString, completionHandler: NobjcObject | 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, completionHandler: NobjcObject): _NSProgress;
+    fetchThumbnailsForItemIdentifiers$requestedSize$perThumbnailCompletionHandler$completionHandler$(itemIdentifiers: _NSArray, size: CGSize, perThumbnailCompletionHandler: NobjcObject | null, completionHandler: NobjcObject | 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

@@ -3,5 +3,5 @@ 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): void;
+    shouldConnectExternalDomainWithCompletionHandler$?(completionHandler: NobjcObject | null): void;
 }

package/dist/FileProvider/NSFileProviderIncrementalContentFetching.d.ts

@@ -1,5 +1,6 @@
 import type { NobjcObject } from "objc-js";
 import type { _NSProgress } from "../Foundation/NSProgress.js";
+import type { _NSString } from "../Foundation/NSString.js";
 import type { _NSURL } from "../Foundation/NSURL.js";
 import type { _NSFileProviderItemVersion } from "./NSFileProviderItemVersion.js";
 import type { _NSFileProviderRequest } from "./NSFileProviderRequest.js";
@@ -7,5 +8,5 @@ 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: number, requestedVersion: _NSFileProviderItemVersion | null, existingContents: _NSURL, existingVersion: _NSFileProviderItemVersion, request: _NSFileProviderRequest, completionHandler: NobjcObject): _NSProgress;
+    fetchContentsForItemWithIdentifier$version$usingExistingContentsAtURL$existingVersion$request$completionHandler$?(itemIdentifier: _NSString, requestedVersion: _NSFileProviderItemVersion | null, existingContents: _NSURL, existingVersion: _NSFileProviderItemVersion, request: _NSFileProviderRequest, completionHandler: NobjcObject | null): _NSProgress;
 }

package/dist/FileProvider/NSFileProviderItem.d.ts

@@ -15,11 +15,11 @@ export interface _NSFileProviderItem {
     /**
      * The identifier of the item. The itemIdentifier should not contain sensitive information, as it may be recorded in system logs and diagnostic files.
      */
-    itemIdentifier?(): number;
+    itemIdentifier?(): _NSString;
     /**
      * The parent identifier specifies the parent of the item in the hierarchy. Set to NSFileProviderRootContainerItemIdentifier for an item at the root of the user's storage. Set to the itemIdentifier of the item's parent otherwise. When enumerating the root container or a generic container, the parentItemIdentifier of the enumerated items is expected to match the enumerated item's identifier. When enumerating the working set, the parentItemIdentifier is expected to match the actual parent of the item in the hierarchy (ie. it is not NSFileProviderWorkingSetContainerItemIdentifier). The parents of trashed items and of the root item are ignored.
      */
-    parentItemIdentifier?(): number;
+    parentItemIdentifier?(): _NSString;
     /**
      * The file or directory name, complete with its file extension. The filename property must not be an empty string, including when the item identifier is NSFileProviderRootContainerItemIdentifier. The filename for NSFileProviderRootContainerItemIdentifier may be displayed in the user interface. Therefore it should be a user-friendly string.
      */

package/dist/FileProvider/NSFileProviderKnownFolderLocation.d.ts

@@ -7,9 +7,9 @@ export declare class _NSFileProviderKnownFolderLocation extends _NSObject {
     /**
      * Initialize a location with the filename of the folder in a specified parent. When replicating a known folder the system will reuse a folder located at the specified filename within the parent if one exists, or create a new item at this location if none exists yet.
      */
-    initWithParentItemIdentifier$filename$(parentItemIdentifier: number, filename: _NSString): _NSFileProviderKnownFolderLocation;
+    initWithParentItemIdentifier$filename$(parentItemIdentifier: _NSString, filename: _NSString): _NSFileProviderKnownFolderLocation;
     /**
      * Initialize a location with the item identifier of a folder that already exists on the server. If the known folder already exists on the server, the provider can specify the exact identifier of the item that needs to be used to back the known folder.
      */
-    initWithExistingItemIdentifier$(existingItemIdentifier: number): _NSFileProviderKnownFolderLocation;
+    initWithExistingItemIdentifier$(existingItemIdentifier: _NSString): _NSFileProviderKnownFolderLocation;
 }

package/dist/FileProvider/NSFileProviderKnownFolderSupporting.d.ts

@@ -4,5 +4,5 @@ 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): void;
+    getKnownFolderLocations$completionHandler$?(knownFolders: NSFileProviderKnownFolders, completionHandler: NobjcObject | null): void;
 }