Struct MapView 

struct MapView {
    rows: Vec<(usize, Yaml)>,
    unresolved: i64,
}

The service map as a call tree rather than a graph.

A terminal draws a tree well and a graph badly, and the tree is the reading that answers the question anyway: what calls what, and where does it start. One line per node, so every line is something Enter can act on — the same shape as the waterfall, which is the other tree in this UI.

Fields

rows: Vec<(usize, Yaml)>

unresolved: i64

Implementations

impl MapView

fn new(y: &Yaml) -> MapView

Depth-first from entry, children by descending call volume.

Volume order rather than name order because the first thing anyone wants out of a service map is the hot path, and it should be the first thing they read. A service reachable by two paths is drawn under the first one reached and not again: a tree with the same subtree in it twice is a tree nobody can count spans off.