import type { _NSArray } from "../Foundation/NSArray.js";
import type { _NSCoder } from "../Foundation/NSCoder.js";
import type { _NSCopying } from "../Foundation/NSCopying.js";
import type { _NSDate } from "../Foundation/NSDate.js";
import type { _NSObject } from "../Foundation/NSObject.js";
import type { _NSSecureCoding } from "../Foundation/NSSecureCoding.js";
import type { _NSString } from "../Foundation/NSString.js";
import type { _CKAsset } from "./CKAsset.js";
import type { _CKRecordID } from "./CKRecordID.js";
import type { _CKRecordValue } from "./CKRecordValue.js";
import type { _CKRecordZoneID } from "./CKRecordZoneID.js";
import type { _CKReference } from "./CKReference.js";
export declare class _CKRecord extends _NSObject {
    static alloc(): _CKRecord;
    static new(): _CKRecord;
    init(): _CKRecord;
    /** This creates the record in the default zone. */
    initWithRecordType$(recordType: _NSString): _CKRecord;
    initWithRecordType$recordID$(recordType: _NSString, recordID: _CKRecordID): _CKRecord;
    initWithRecordType$zoneID$(recordType: _NSString, zoneID: _CKRecordZoneID): _CKRecord;
    /**
     * @discussion In addition to @c objectForKey: and @c setObject:forKey:, dictionary-style subscripting (@c record[key] and @code record[key] = value @endcode) can be used to get and set values. Acceptable value object classes are: - CKReference - CKAsset - CLLocation - NSData - NSDate - NSNumber - NSString - NSArray containing objects of any of the types above Any other classes will result in an exception with name @c NSInvalidArgumentException. Whenever possible, value objects will be copied when set on a record. Field keys starting with '_' are reserved. Attempting to set a key prefixed with a '_' will result in an error. Key names roughly match C variable name restrictions. They must begin with an ASCII letter and can contain ASCII letters and numbers and the underscore character. The maximum key length is 255 characters.
     */
    objectForKey$(key: _NSString): _CKAsset | _CKReference | null;
    setObject$forKey$(object_: _CKRecordValue | null, key: _NSString): void;
    allKeys(): _NSArray;
    /**
     * @abstract A special property that returns an array of token generated from all the string field values in the record. @discussion These tokens have been normalized for the current locale, so they are suitable for performing full-text searches.
     */
    allTokens(): _NSArray;
    objectForKeyedSubscript$(key: _NSString): _CKAsset | _CKReference | null;
    setObject$forKeyedSubscript$(object_: _CKRecordValue | null, key: _NSString): void;
    /** A list of keys that have been modified on the local CKRecord instance */
    changedKeys(): _NSArray;
    /**
     * @discussion @c CKRecord supports @c NSSecureCoding. When you invoke @c encodeWithCoder: on a @c CKRecord, it encodes all its values. Including the record values you've set. If you want to store a @c CKRecord instance locally, AND you're already storing the record values locally, that's overkill. In that case, you can use @c encodeSystemFieldsWithCoder:. This will encode all parts of a @c CKRecord except the record keys / values you have access to via the @c changedKeys and @c objectForKey: methods. If you use @c initWithCoder: to reconstitute a @c CKRecord you encoded via @c encodeSystemFieldsWithCoder:, then be aware that - any record values you had set on the original instance, but had not saved, will be lost - the reconstituted CKRecord's @c changedKeys will be empty
     */
    encodeSystemFieldsWithCoder$(coder: _NSCoder): void;
    /**
     * Convenience wrappers around creating a @c CKReference to a parent record. The resulting @c CKReference will have @code referenceAction = CKReferenceActionNone @endcode
     */
    setParentReferenceFromRecord$(parentRecord: _CKRecord | null): void;
    setParentReferenceFromRecordID$(parentRecordID: _CKRecordID | null): void;
    recordType(): _NSString;
    recordID(): _CKRecordID;
    /**
     * Change tags are updated by the server to a unique value every time a record is modified. A different change tag necessarily means that the contents of the record are different.
     */
    recordChangeTag(): _NSString | null;
    /** This is a User Record recordID, identifying the user that created this record. */
    creatorUserRecordID(): _CKRecordID | null;
    creationDate(): _NSDate | null;
    /**
     * This is a User Record recordID, identifying the user that last modified this record.
     */
    lastModifiedUserRecordID(): _CKRecordID | null;
    modificationDate(): _NSDate | null;
    /**
     * @discussion The share property on a record can be set by creating a share using @code -[CKShare initWithRootRecord:] @endcode. The share property on a record will be removed when the corresponding CKShare is deleted from the server. Send this record in the same batch as the share delete and this record's share property will be updated. Sharing is only supported in zones with the @c CKRecordZoneCapabilitySharing capability. The default zone does not support sharing. If any records have a parent reference to this record, they are implicitly shared alongside this record. Note that records in a parent chain must only exist within one share. If a child record already has a share reference set then you will get a @c CKErrorAlreadyShared error if you try to share any of that record's parents. Child records can be shared independently, even if they have a common parent. For example: Record A has two child records, Record B and Record C. A / \ B C These configurations are supported: - Record A part of Share 1, or - Record B part of Share 1, or - Record C part of Share 1, or - Record B part of Share 1, Record C part of Share 2 These configurations are not supported: Record A part of Share 1, Record B part of Share 2, or -- This is not allowed because Record B would then be in two shares; Share 1 by being Record A's child, and Share 2 Record A part of Share 1, Record C part of Share 2, or -- This is not allowed because Record C would then be in two shares; Share 1 by being Record A's child, and Share 2 Record A part of Share 1, Record B part of Share 2, Record C part of Share 3 -- This is not allowed because both Record B and Record C would then each be in two shares. Whenever possible, it is suggested that you construct your parent hierarchies such that you will only need to share the topmost record of that hierarchy.
     */
    share(): _CKReference | null;
    /**
     * @abstract Use a parent reference to teach CloudKit about the hierarchy of your records. @discussion When a record is shared, all children of that record are also shared. A parent record reference must have @c CKReferenceActionNone set. You can create a separate reference with @c CKReferenceActionDeleteSelf if you would like your hierarchy cleaned up when the parent record is deleted. The target of a parent reference must exist at save time - either already on the server, or part of the same @c CKModifyRecordsOperation batch. You are encouraged to set up the @c parent relationships as part of normal record saves, even if you're not planning on sharing records at this time. This allows you to share and unshare a hierarchy of records at a later date by only modifying the "top level" record, setting or clearing its @c share reference.
     */
    parent(): _CKReference | null;
    setParent$(value: _CKReference | null): void;
    /**
     * Any values set here will be locally encrypted before being saved to the server and locally decrypted when fetched from the server. Encryption and decryption is handled by the CloudKit framework. Key material necessary for decryption are available to the owner of the record, as well as any users that can access this record via a CKShare. All CKRecordValue types can be set here except CKAsset and CKReference.
     */
    encryptedValues(): _CKRecord;
}
export interface _CKRecord extends _NSSecureCoding, _NSCopying {
}
