Whether this host may arm/disarm breakpoints from the selected-step control. Off by default — the run view also renders where those controls would be wrong.
Intent only — the host owns SetBreakpoints.
A connection was clicked. EdgeID is the dependency row id when the projection carried one.
Intent only — the host owns OverrideEdge.
Height of the canvas. Hosts embed this in very different amounts of space.
The parent bag's data / context roots, for the Invocation scope.
The legend was toggled from the toolbar, so a host can remember the choice.
What each running step says it is doing, from NodeProgress frames. Keyed by task row id.
Keep re-reading while the graph is still moving.
Off by default: most hosts show a finished run, and a component that polls by default would have every historical run quietly issuing queries forever.
Stable overlay object — rebuilt only when debug inputs change, so the editor does not re-project every CD cycle.
How often to re-read while live. Seconds, not milliseconds — this is a human-scale view.
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.
The last step the person selected, so the breakpoint control has a target.
Emitted once, when every step has reached a terminal status.
Compact debug key under the summary line. Off unless the host is a debugger.
Whether the canvas legend shows. Off by default here, unlike the editor.
The legend explains the authoring vocabulary — what a conditional edge means, what a duplicate default looks like. That is what someone drawing a graph needs. A run view answers a different question, "what happened", which the legend helps with not at all while covering a corner of the canvas the graph is usually occupying.
Whether the canvas toolbar rides above the graph.
Debug and other run hosts leave this on and set ToolbarVisibility to minimized so the
graph is the picture, not a floating tool strip. The chip in the corner restores the bar.
VS Code VARIABLES pane to the left of the canvas. Off unless the host is debugging.
Name shown on the compiled graph. Purely cosmetic; the rows carry the truth.
StaticɵdirStaticɵfacArmed breakpoint task IDs, from the parent row's $.debug.breakpoints. Empty by default so
embeds (agent-run timeline, test harness) never grow debugger chrome they did not ask for.
Steps in a terminal state, for the host's summary line. Uses the same map the canvas paints.
Operator-forced edge verdicts, keyed by MJ: Task Dependencies row ID.
Canvas extent, so a host can size its container to the graph rather than guessing.
The graph is claim-gated. Combined with PausedAtTaskID so start-paused (no specific
step yet) can still light the entry node as waiting.
The latest live dispatcher frame, handed in by the host.
The host owns the subscription (GraphQLDataProvider.TaskGraphFrames or anything shaped like
it) and binds each arrival here; the widget folds it into the overlay. Frames are advisory —
a task frame patches the node's status in place for sub-second feedback, and the frames that
imply CASCADES (a skip, a block, settlement) trigger a debounced row reload, because the
dispatcher's propagation writes rows this component cannot infer from one frame. Rows remain
the truth; the existing poll (if enabled) remains the safety net.
The graph to watch — the parent MJ: Tasks row that represents it.
Setter-based rather than ngOnChanges, matching the editor beside it: the reaction is
explicit and costs nothing on unrelated change-detection passes.
The step a breakpoint actually stopped on.
Left data pane + split sizes. One JSON bag in MJ: User Settings.
Returns either the default Metadata provider or the one specified in the Provider property, if it was specified
Replay: render the run as it stood at this moment, reconstructed from each step's
StartedAt/CompletedAt. Null (the default) renders the present. A step that had not
started reads Pending; one mid-flight reads In Progress; one already finished reads its
final status — the same three answers the rows would have given a viewer at that time.
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
A callback method that performs custom clean-up, invoked immediately before a directive, pipe, or service instance is destroyed.
Debug attaches here: replace Edit/Remove with breakpoint / path-override items.
A node was selected on the canvas.
The projected tempId IS the task id, so the row lookup is exact — and handing the host the
whole task rather than an id spares every host from re-reading a row this component already
holds.
Base class for all Angular components in the MemberJunction system.