Use BreadcrumbNavigate.
The same emitter under the old binding name, so a template still binding (breadcrumbNavigate) keeps working. Must stay AFTER BreadcrumbNavigate: class fields initialise in order, and the other way round this captures undefined.
Emitted when user navigates via breadcrumb
Whether the user may edit this dashboard. An empty dashboard then offers Add part in view mode too; the host decides how to get into edit mode.
All categories for breadcrumb path resolution
Emitted when dashboard configuration changes
Use DashboardSaved.
The same emitter under the old binding name, so a template still binding (dashboardSaved) keeps working. Must stay AFTER DashboardSaved: class fields initialise in order, and the other way round this captures undefined.
Emitted when the dashboard is saved
Use EditModeChanged.
The same emitter under the old binding name, so a template still binding (editModeChanged) keeps working. Must stay AFTER EditModeChanged: class fields initialise in order, and the other way round this captures undefined.
Emitted when edit mode changes
Emitted when an error occurs
Use LayoutDeferred.
The same emitter under the old binding name, so a template still binding (layoutDeferred) keeps working. Must stay AFTER LayoutDeferred: class fields initialise in order, and the other way round this captures undefined.
Emitted when layout initialization is deferred because the container cannot be initialized yet.
Use LayoutLifecycle.
The same emitter under the old binding name, so a template still binding (layoutLifecycle) keeps working. Must stay AFTER LayoutLifecycle: class fields initialise in order, and the other way round this captures undefined.
Emitted as the Golden Layout viewer moves through dashboard/layout readiness states.
Use LayoutReady.
The same emitter under the old binding name, so a template still binding (layoutReady) keeps working. Must stay AFTER LayoutReady: class fields initialise in order, and the other way round this captures undefined.
Emitted once Golden Layout has initialized with a non-zero container and updated its size.
Use NavigationRequested.
The same emitter under the old binding name, so a template still binding (navigationRequested) keeps working. Must stay AFTER NavigationRequested: class fields initialise in order, and the other way round this captures undefined.
Emitted when a panel requests navigation to another resource
Use OpenInTab.
The same emitter under the old binding name, so a template still binding (openInTab) keeps working. Must stay AFTER OpenInTab: class fields initialise in order, and the other way round this captures undefined.
Emitted when user clicks "Open in Tab" button
Use PanelInteraction.
The same emitter under the old binding name, so a template still binding (panelInteraction) keeps working. Must stay AFTER PanelInteraction: class fields initialise in order, and the other way round this captures undefined.
Emitted when a panel interaction occurs
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.
Whether to show the breadcrumb navigation
Whether to show the Edit button
Whether to show the "Open in Tab" button (for embedded dashboards)
StaticɵdirStaticɵfacUse AutoSave.
Use Dashboard.
Use DashboardId.
Alternative: Load dashboard by ID
Use HasPanels.
Helper to check if layout has any panels (for template use). Panels are stored in componentState within the layout tree.
Use HasUnsavedChanges.
Use IsEditing.
Use LayoutContainer.
Use PartTypes.
Returns either the default Metadata provider or the one specified in the Provider property, if it was specified
Returns either the default RunQuery provider or the one specified in the Provider property, if it was specified
Returns either the default RunView provider or the one specified in the Provider property, if it was specified
Use ShouldShowToolbar.
Computed: Should the toolbar be visible? Auto-hides when showToolbar=false OR when all toolbar elements are disabled
Use ShowBreadcrumb.
Use ShowEditButton.
Use ShowOpenInTabButton.
Use ShowToolbar.
Optionalicon: stringOptionallocation: PanelPositionUse AddPanel.
Adds a panel and returns its id, or null when nothing was added (no layout yet, or an unknown part type). With a location, the layout editor places the panel there and the layout is rebuilt; without one, Golden Layout adds the panel to its first stack.
Optionalicon: stringOptionallocation: PanelPositionShows layout: stores it as the dashboard's layout, rebuilds the panels, marks the dashboard
changed and emits a layout config change. Build the layout with the layout editor functions.
Rejects when the rebuild fails, for example when the container stays at zero size.
Confirm removal of a panel (called by parent after confirmation dialog)
Get the current configuration
Get a panel by ID. Extracts panel from the layout's componentState (single source of truth).
The panel's address in the layout, for example row/1 › tab 0, or null when it is not in the layout.
Use GetPartTypes.
Get available part types
True when the dashboard's saved layout differs from the one this viewer last loaded or saved, for example after another tab saved the dashboard.
A saved copy of the shown dashboard. Defaults to the shown dashboard.
A callback method that performs custom clean-up, invoked immediately before a directive, pipe, or service instance is destroyed.
Use OnAddPanelClick.
Handle add panel button click - emits event for parent to show dialog
Use OnOpenInTabClick.
Handle "Open in Tab" button click - emits event for the parent to open the dashboard in a dashboard tab
Use RefreshAllPanels.
Refresh all panels
Shows the dashboard's saved layout again and drops unsaved layout changes. The current layout is removed at once, so an edit-mode change made right after the call applies to the new layout. A hidden viewer builds the layout when its container gets a size, with no time limit.
A saved copy of the shown dashboard to show instead. Defaults to the shown dashboard.
Remove a panel from the dashboard. Panels live in GL's componentState, so removing from GL removes the panel.
Save the current dashboard configuration
Use ToggleEditMode.
Toggle edit mode
Optionaltitle: stringOptionalicon: stringUse UpdatePanelConfig.
Update a panel's configuration. Since panels live in componentState within the layout, we need to update the layout tree directly or reinitialize with updated data. Resolves once the layout is rebuilt with the updated panel; rejects when the rebuild fails.
Optionaltitle: stringOptionalicon: stringTakes another copy of the shown dashboard without rebuilding the layout, for example after DashboardEngine reloaded its dashboards. Later saves write that copy. Returns false, and changes nothing, when the copy is of another dashboard or its saved layout differs from the one this viewer last loaded or saved (use ReloadFromSaved then).
Use WaitForLayoutReady.
Resolves when the current dashboard's Golden Layout instance has initialized against a non-zero container and completed its first size update.
Main dashboard viewer component. Renders a configurable dashboard with draggable/resizable panels using Golden Layout.
This component is GENERIC and has no routing dependencies. Navigation events are bubbled up for the parent component to handle.