Member Junction
    Preparing search index...

    The Calendar view type (IViewRenderer): records placed on a day, week (Monday first) or month layout by a start field and an optional end field named in the view's CalendarViewConfig. Placement is the pure logic in calendar-placement.ts; this component only holds the anchor date and binds the result.

    Like Map, it asks the host for the full record set (dataRequest({ loadAll: true })), so it sees up to the host's load-all cap rather than one page. Clicking a record emits recordSelected and double-clicking emits recordOpened, as the Cards renderer does. A gear button opens the CalendarViewPropSheetComponent inline, because no host mounts a descriptor's prop sheet yet.

    Inputs/outputs use the camelCase names the IViewRenderer contract mandates.

    Hierarchy (View Summary)

    Implements

    Index

    Constructors

    Properties

    Anchor: Date = ...

    A date inside the period on screen.

    configChanged: EventEmitter<CalendarViewConfig> = ...

    Emitted with the full config when the layout or the settings change.

    dataRequest: EventEmitter<ViewDataRequest> = ...

    Asks the host for the full record set on init.

    filterText: string | null = null

    Active filter text. Accepted for contract uniformity; the host pre-filters records.

    HasDateFields: boolean = false

    Whether the entity has any date field.

    MaxItemsPerCell: 3

    Month cells shown before "+N more".

    Mode: CalendarMode = 'month'

    The current layout.

    ModeOptions: { key: string; label: string }[] = ...

    The layout switch options.

    MonthWeeks: Date[][] = []

    The month grid's weeks.

    Provider: IMetadataProvider | null

    If specified, this provider will be used for communication and for all metadata purposes. By default, if not provided, the Metadata and RunView classes are used for this and the default GraphQLDataProvider is used which is connected to the same back-end MJAPI instance as the Metadata and RunView classes. If you want to have this component connect to a different MJAPI back-end, create an instance of a ProviderBase sub-class like GraphQLDataProvider/etc, and configure it as appropriate to connect to the MJAPI back-end you want to use, and then pass it in here.

    recordOpened: EventEmitter<unknown> = ...

    Emitted on a record double-click with the raw record (a navigation request).

    recordSelected: EventEmitter<unknown> = ...

    Emitted on a record click with the raw record.

    selectedRecordId: string | null = null

    Primary-key string of the selected record. Accepted for contract uniformity.

    ShowSettings: boolean = false

    Whether the inline settings sheet is open.

    VisibleDays: Date[] = []

    The days of the day/week layout.

    WeekDayLabels: string[] = CALENDAR_WEEK_DAYS

    Monday-first weekday labels.

    "ɵdir": unknown
    "ɵfac": ɵɵFactoryDeclaration<BaseAngularComponent, never>

    Accessors

    • get ProviderToUse(): IMetadataProvider

      Returns either the default Metadata provider or the one specified in the Provider property, if it was specified

      Returns IMetadataProvider

    • get RunQueryToUse(): IRunQueryProvider

      Returns either the default RunQuery provider or the one specified in the Provider property, if it was specified

      Returns IRunQueryProvider

    • get RunViewToUse(): IRunViewProvider

      Returns either the default RunView provider or the one specified in the Provider property, if it was specified

      Returns IRunViewProvider

    Methods