@umbraco-cms/backoffice
    Preparing search index...

    Class UmbContentCollectionConfigurationContext

    Resolves the configuration of a content collection, for any host that can say which collection it renders, which data type configures it and which entity it is scoped to.

    Hierarchy (View Summary)

    Index
    collectionAlias: Observable<string | undefined> = ...

    The alias of the collection to render, e.g. Umb.Collection.Document. Undefined means the host has no collection concept at all.

    collectionConfig: Observable<UmbCollectionConfiguration | undefined> = ...

    The resolved collection configuration, or undefined while it is loading and when no collection is configured.

    dataType: Observable<UmbDataTypeDetailModel | undefined> = ...

    The resolved configuration data type. Exposed so hosts can derive presentation of their own from it — a workspace view reads its icon and label from here — without that presentation concern moving into this context.

    dataTypeUnique: Observable<string | undefined> = ...

    The data type configuring the collection, taken from the content type's collection reference. Undefined means no collection is configured.

    hasCollection: Observable<boolean> = ...

    Whether a collection should be rendered at all. True only once both a collection alias and a configuring data type are known.

    unique: Observable<UmbEntityUnique | undefined> = ...

    The entity the collection is scoped to. null is the root; undefined means there is no subject at all, which is the case for a content type without a hierarchy.

    • The addEventListener() method of the EventTarget interface sets up a function that will be called whenever the specified event is delivered to the target.

      MDN Reference

      Parameters

      • type: string
      • callback: EventListenerOrEventListenerObject | null
      • Optionaloptions: boolean | AddEventListenerOptions

      Returns void

    • The dispatchEvent() method of the EventTarget sends an Event to the object, (synchronously) invoking the affected event listeners in the appropriate order. The normal event processing rules (including the capturing and optional bubbling phase) also apply to events dispatched manually with dispatchEvent().

      MDN Reference

      Parameters

      • event: Event

      Returns boolean

    • The removeEventListener() method of the EventTarget interface removes an event listener previously registered with EventTarget.addEventListener() from the target. The event listener to be removed is identified using a combination of the event type, the event listener function itself, and various optional options that may affect the matching process; see Matching event listeners for removal.

      MDN Reference

      Parameters

      • type: string
      • callback: EventListenerOrEventListenerObject | null
      • Optionaloptions: boolean | EventListenerOptions

      Returns void