import { SchemaOptions } from './validate/validate';
export interface DomainObjectInstantiationOptions {
    /**
     * allow callers to skip certain aspects of instantiation
     *
     * e.g., for performance optimizations in specific usecases
     */
    skip?: {
        /**
         * allow callers to skip schema validation
         *
         * usecase examples
         * - deserialize: schema validation increases deserialization time dramatically (10-100x) (especially if using Joi, that thing is slow!)
         */
        schema?: boolean;
    };
}
/**
 * Domain Object
 *
 * Responsibilities:
 * - optionally validate the properties that are passed into the constructor against the schema at runtime, if schema is supplied
 * - assign all properties that are passed into constructor to self, after optional runtime validation
 */
export declare class DomainObject<T extends Record<string, any>> {
    constructor(props: T, options?: DomainObjectInstantiationOptions);
    /**
     * DomainObject.alias
     *
     * When set, declares the alias via which domain objects of this class are known to be referred to.
     *
     * For example
     * - PlantPot.alias = 'pot'
     * - Bird.alias = { singular: 'bird', plural: 'flock' }
     *
     * Relevance
     * - formalizes that we can expect to see the dobj referred to by this alias
     * - enables code generators to use this colloquial alias in contracts for better devex
     */
    static alias?: string | {
        plural?: string;
        singular?: string;
    };
    /**
     * DomainObject.schema
     *
     * When set, will be used to validate the properties passed into the constructor at runtime (i.e., during instantiation)
     *
     * Supports [`Zod`](https://github.com/colinhacks/zod), [`Joi`](https://github.com/sideway/joi), and [`Yup`](https://github.com/jquense/yup)
     */
    static schema?: SchemaOptions<any>;
    /**
     * DomainObject.nested
     *
     * When set, will be used to hydrate nested DomainObjects. This is especially useful when instantiating nested domain objects from data stores (e.g., apis or databases). This is _required_ in order to safely use the `serialize` and `getUniqueIdentifier` functions - as those functions check static properties of domain objects to function correctly.
     *
     * For example:
     * ```ts
     * // define the plant pot
     * interface PlantPot {
     *   diameterInInches: number;
     * }
     * class PlantPot extends DomainObject<PlantPot> implements PlantPot {}
     *
     * // define the plant owner
     * interface PlantOwner {
     *   diameterInInches: number;
     * }
     * class PlantOwner extends DomainObject<PlantOwner> implements PlantOwner {}
     *
     * // define the plant
     * interface Plant {
     *   pot: PlantPot;
     *   owners: PlantOwner[];
     *   lastWatered: string;
     * }
     * class Plant extends DomainObject<Plant> implements Plant {
     *   public static nested = { pot: PlantPot, owners: PlantOwner }
     * }
     *
     * // and show that it hydrates the plant pot
     * const plant = new Plant({ pot: { diameterInInches: 7 }, owners: [{ name: 'bob' }], lastWatered: 'monday' }); // notice how the param of `pot` we're inputting is _not_ an instance of `PlantPot`, and `owners` are not instances of `PlantOwner`
     * expect(plant.pot).toBeInstanceOf(PlantPot); // now succeeds, as during instantiation we hydrated `pot` into an instance of `PlantPot`, due to `Plant.nested.pot` being set
     * plant.owners.forEach((owner) => expect(owner).toBeInstance(PlantOwner)); // also succeeds, since during instantiation we hydrated each `owner` into an instance of `PlantOwner`, due to `Plant.nested.owners` being set
     * ```
     */
    static nested?: Record<string, DomainObject<any>>;
    /**
     * DomainObject.metadata
     *
     * When set, customizes the keys that are considered as metadata of this domain object.
     *
     * Context,
     * - domain objects are often persisted inside of storage mechanisms that assign metadata to them, such as ids or timestamps
     * - metadata simply adds information _about_ the object, without contributing to _defining_ the object
     *
     * Relevance,
     * - metadata properties do not contribute to the unique key of a DomainLiteral
     * - metadata properties can be easily stripped from an object by using the `omitMetadataValues` method
     *
     * By default,
     * - `id`, `createdAt`, `updatedAt`, and `effectiveAt` are considered metadata keys
     * - `uuid` is also considered a metadata key, if it is not included in the unique key of the DomainEntity or DomainEvent
     */
    static metadata: readonly string[];
}