import type { IClientSideManifestBase } from './IClientSideManifestBase';
import type { IClientSideComponentManifest } from './IClientSideComponentManifest';
/**
 * Multi-version manifests are defined by this interface.
 *
 * @remarks
 *
 * The schema of this manifest is owned and versioned by Microsoft. Following rules should be followed while changing
 * this schema. This set of rules can also be called the "manifest upgrade rules".
 *
 * -  For minor changes, new properties can be added to this schema in a backwards-compatible way. i.e. the code
 *    that processes the manifest should be able to handle the absence of those new properties.
 *
 * -  Try to model your changes as minor SemVer increments.  Major version changes should be avoided because they
 *    impose a migration cost on developers.
 *
 * -  The 'manifestVersion' should be bumped for all small or big changes.
 *
 * @privateRemarks
 *
 * This schema should be at all times kept in sync with the server-side code file
 * SPClientSideMultiVersionManifest.cs.
 *
 * @alpha
 */
export interface IClientSideMultiVersionManifest<TManifest extends IClientSideComponentManifest> extends IClientSideManifestBase {
    /**
     * A mapping of version numbers to manifests. This field is used to roll all versions of a component
     * together into a single manifest.
     *
     * @remarks
     *
     * Supported values: Mapping of version strings to manifest bodies
     *
     * Example:
     * ```
     *  {
     *    "1.0.0": ...manifest,
     *    "2.0.0": ...manifest
     *  }
     * ```
     */
    versions: {
        [versionNumber: string]: TManifest;
    };
}
//# sourceMappingURL=IClientSideMultiVersionManifest.d.ts.map