Protecteddestroy$Snapshot of Store.Tabs, reassigned by every handler. A getter delegating to the store
returns a FRESH array per read, which both defeats the strip's OnPush change detection and
trips dev-mode ExpressionChanged under default CD — the classic unstable-binding bug.
ReadonlyLabelsOne source of labels for both strips — the comparison is worthless if they differ.
ProtectednavigationTab ID for query param notification scoping. Set by resource wrappers that render child dashboards, so the child knows which tab it belongs to. If not set, falls back to Data.Configuration.tabId.
Drives the projected strip.
The projected strip's tabs, as mutable state: mj-tabstrip owns no tab array, so CLOSING a
tab means the host removing it from the list it renders — a close with no (BeforeTabClosed)
handler waits forever on the strip's cancelable-close contract and silently does nothing.
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.
ReadonlyStoreDrives the data-driven strip. Uses the real store rather than a hand-rolled array so the fixture also exercises open/close/reorder/neighbour-activation as shipped.
StaticɵdirStaticɵfacReturns 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
ProtectedGetRead current query params from tab configuration. Use in initDashboard() / ngOnInit() to get initial URL state.
Get this component's tab ID. Checks ParentTabId input first (set by resource wrappers for child dashboards), then falls back to Data.Configuration.tabId.
True when this resource holds in-progress user edits that a silent replacement would destroy. Consulted by the shell before consuming a temporary record tab under the preview-tab model (see TabRequest.TempScope): an editing tab is never replaced — the next open lands in its own tab instead, so the edit survives.
Default false: most resources are read-only surfaces with nothing to lose. Resources that host an editable form override it.
A callback method that performs custom clean-up, invoked immediately before a directive, pipe, or service instance is destroyed.
A callback method that is invoked immediately after the default change detector has checked the directive's data-bound properties for the first time, and before any of the view or content children have been checked. It is invoked only once when the directive is instantiated.
ProtectedNotifyAsk the host shell to close/dismiss this resource (typically: close the tab). Called by subclasses that hosted a form that emitted a 'dismiss' navigation event — most often, a brand-new record where the user clicked Discard. The record was never saved, the form is empty, and leaving it open serves no purpose. The tab-container listens for this and closes the workspace tab.
ProtectedNotifyCall this to notify the tab system that the resource's display name has changed. The tab container will update the tab title and browser title accordingly.
ProtectedNotifyProtectedNotifyComplete the strip's close contract: (TabClosed) hands the host a done callback and the
strip's CloseTab awaits it — the host removes the tab from ITS list (the strip owns no tab
array) and signals done. Without a handler the promise never settles and the close button
(and the Delete key) silently do nothing — the exact contract this page exists to demonstrate.
ProtectedOnCalled by the framework when query params change from an external source (browser back/forward, deep link navigation). Override in subclasses to react to query param changes.
The new query params from the URL
'popstate' for back/forward, 'deeplink' for external URL entry
ProtectedonHook for a host that instantiates CHILD resource components: re-home them here.
A host stamps its children with its tab id when it creates them, which is a SNAPSHOT. A cache reattach moves the host to a different tab without recreating anything, so a child left holding the birth tab's id would go on reading and — worse — writing that tab's params from inside a tab it no longer belongs to. That is the same cross-tab corruption this class refuses elsewhere, just arriving by a slower route, so the stamp has to move when the host does.
Default is a no-op: a component with no children has nothing to re-home.
Re-home this component to a different tab (cache reattach across tab ids). Replaces the reactive param subscription with one bound to the new tab and resets the duplicate-delivery key so the new tab's CURRENT params apply as a fresh mount would — the replay-on-subscribe delivers them immediately.
ProtectedRefreshMarks this component's view (and its ancestors) as needing change detection and schedules a tick — the reliable way for a resource component to re-render after updating state from async work (RunView/RunQuery continuations, timers, websocket pushes, RxJS subscriptions).
WHY THIS EXISTS: the Explorer shell hosts resource components dynamically — createComponent()
ApplicationRef.attachView() — because tab content mounts into Golden Layout / cached DOM
containers, not into an Angular template. Since Angular 18's change-detection scheduler
rework (Explorer is on Angular 21), ApplicationRef.tick() only refreshes attached views
that are FLAGGED dirty; a root-level attached view whose component mutates plain fields from
an async continuation is never flagged, so the view silently never re-renders — even though
the component uses default (non-OnPush) change detection (issue #3106).The framework calls this automatically from NotifyLoadStarted() / NotifyLoadComplete(), so the standard load lifecycle re-renders without any subclass action. Call it yourself after any LATER async state change that must reach the DOM outside those signals.
ProtectedrehomeRe-homes a child this component created to tabId.
The ParentTabId stamp is cleared FIRST and deliberately: getTabId() prefers it over the
rebound id, so leaving the old stamp in place would make the child's own RebindTabId a
no-op — it early-returns when getTabId() already matches — and the child would keep
answering with the tab it was born in. Clearing it lets the rebind be the authority, and the
child re-delivers the NEW tab's current params exactly as a fresh mount would.
Seeded so every per-tab state the chrome can express is on screen at once — a plain tab, one with unsaved edits (dot), one rejected (warning tint + icon), one complete. Otherwise the states that only appear mid-workflow are the ones that quietly drift.
ProtectedResourceProtectedUpdatePush query param changes to the URL. Creates a browser history entry. Safe to call during OnQueryParamsChanged — auto-suppressed to prevent loops.
The write is ALWAYS scoped to this component's own tab. A component that cannot identify its tab does not write at all — see the guard below.
Tab Strip Lab — MJ's two tab strips, rendered side by side over the SAME labels.
They are two components on purpose:
mj-tabstriptakes tabs as projected children and addresses them by position (it owns their bodies), whilemj-workspace-tab-striptakes a data array and addresses it by stable id (it projects nothing). Those are genuinely different API contracts. What they must NEVER differ on is how a tab looks or how it responds to a keyboard — and that is exactly the kind of drift no unit test catches and nobody notices until two screens sit side by side. Hence this page: the same four labels through both, so any divergence is immediate.Both get their chrome from the one global
.mj-tabs*stylesheet and their keyboard behaviour from the onemjTabListdirective, so a difference visible here is a bug in that sharing.🚨 SAFETY BOUNDARY: deliberately unwired from agent context and client tools, as a developer fixture rather than a data surface (the GraphQL Console precedent). It reads and writes nothing.