fix(cli): single-key note rows render as raw indented lines under their step (Task 14 review)
This commit is contained in:
@@ -18,13 +18,18 @@ namespace ZB.MOM.WW.ScadaBridge.CLI.Commands;
|
||||
/// to the generic renderer unprojected, the object takes the Property/Value branch and the
|
||||
/// whole event array lands in one cell as raw JSON. This projects the events through the same
|
||||
/// <see cref="FlowGraphBuilder"/> the Flow Debugger page uses and prints one row per STEP —
|
||||
/// <c>occurred | kind | lane | target | durationMs | status | lifecycle | correlation | error</c> — in the
|
||||
/// order the page draws them, so a terminal user can read the swimlane top-to-bottom. An
|
||||
/// <c>occurred | kind | lane | target | durationMs | status | lifecycle | correlation | error | logs</c> —
|
||||
/// in the order the page draws them, so a terminal user can read the swimlane top-to-bottom. An
|
||||
/// outbound operation's rows (a cached call's Submit → Forwarded → Attempted → Resolve, a
|
||||
/// notification's Send → Deliver) fold into ONE row whose <c>lifecycle</c> column counts them
|
||||
/// and whose <c>status</c> is the latest row's (outbound-calls plan 2026-09-06, D3). A trailing
|
||||
/// <c>note</c> row reports a failed / incomplete run (with the error code verbatim, e.g.
|
||||
/// <c>STANDBY_NODE</c>) or a truncated event list.
|
||||
/// and whose <c>status</c> is the latest row's (outbound-calls plan 2026-09-06, D3). <c>logs</c>
|
||||
/// counts the step's attached <c>ScriptLog</c> lines (step-logs design 2026-09-09); passing
|
||||
/// <c>showLogs</c> additionally prints those lines, and a failed step's exception detail, as
|
||||
/// raw indented lines immediately under that step's row — <see cref="CommandHelpers"/>'s table
|
||||
/// renderer special-cases a single-property <c>{ "note": … }</c> row to print it that way
|
||||
/// instead of padding it into a table cell. A trailing <c>note</c> row (the same special case)
|
||||
/// reports a failed / incomplete run (with the error code verbatim, e.g. <c>STANDBY_NODE</c>)
|
||||
/// or a truncated event list.
|
||||
/// </para>
|
||||
///
|
||||
/// <para>JSON output is never touched — <c>--format json</c> gets the full raw result.</para>
|
||||
@@ -179,7 +184,7 @@ internal static class FlowDebugTableProjection
|
||||
/// <summary>Formats one <see cref="FlowLogLine"/> as <c> HH:mm:ss.fff LEVEL source message</c> (UTC, level upper-cased and padded to 5 chars).</summary>
|
||||
private static string FormatLogLine(FlowLogLine line)
|
||||
{
|
||||
var time = line.OccurredAtUtc.UtcDateTime.ToString("HH:mm:ss.fff", CultureInfo.InvariantCulture);
|
||||
var time = line.OccurredAtUtc.ToUniversalTime().ToString("HH:mm:ss.fff", CultureInfo.InvariantCulture);
|
||||
var level = (line.Level ?? "info").ToUpperInvariant().PadRight(5);
|
||||
return $" {time} {level} {line.Source} {line.Message}";
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user