/**
 * Bungie.Net API
 * These endpoints constitute the functionality exposed by Bungie.net, both for more traditional website functionality and for connectivity to Bungie video games and their related functionality.
 *
 * OpenAPI spec version: 2.18.0
 * Contact: support@bungie.com
 *
 * OODestiny Version: 2.0.9
 * NOTE: This class is auto generated by the oodestiny code generator program
 * Repository: {@link https://github.com/owensimpson/oodestiny}
 * Adapted from {@link https://github.com/DestinyItemManager/bungie-api-ts}
 * Do not edit these files manually.
 */
import { DestinyMilestoneActivityVariantDefinition } from './DestinyMilestoneActivityVariantDefinition';
/**
 * Milestones can have associated activities which provide additional information
 * about the context, challenges, modifiers, state etc... related to this Milestone.
 *
 *
 * Information we need to be able to return that data is defined here, along with
 * Tier data to establish a relationship between a conceptual Activity and its
 * difficulty levels and variants.
 * @see {@link https://bungie-net.github.io/#/components/schemas/Destiny.Definitions.Milestones.DestinyMilestoneActivityDefinition}
*/
export interface DestinyMilestoneActivityDefinition {
    /**
     * The "Conceptual" activity hash. Basically, we picked the lowest level activity
     * and are treating it as the canonical definition of the activity for rendering
     * purposes.
     *
     * If you care about the specific difficulty modes and variations, use the
     * activities under "Variants". Mapped to DestinyActivityDefinition in the manifest.
    */
    readonly conceptualActivityHash: number;
    /**
     * A milestone-referenced activity can have many variants, such as Tiers or
     * alternative modes of play.
     *
     * Even if there is only a single variant, the details for these are represented
     * within as a variant definition.
     *
     * It is assumed that, if this DestinyMilestoneActivityDefinition is active, then
     * all variants should be active.
     *
     * If a Milestone could ever split the variants' active status conditionally, they
     * should all have their own DestinyMilestoneActivityDefinition instead! The
     * potential duplication will be worth it for the obviousness of processing and use.
     * Mapped to DestinyActivityDefinition in the manifest.
    */
    readonly variants: {
        [key: number]: DestinyMilestoneActivityVariantDefinition;
    };
}