Sections: Request / Response / Message & consumer / Client — each built
from catalog entries with a non-empty path, bucketed by the path's
leading namespace segment (pathNamespace), with family entries
(http_*, arg_*, ...) expanding into indented {{...}} sub-rows for
every concrete member suggestions discovered once a trace snapshot is
available (availability === 'ok') — see PathFamilyTable /
pathFamilyMembers. Then Environment (names only, from the env
suggestion group). Then a flat Legacy $var mapping table covering every
catalog entry by its old name, for looking up what an existing $foo in
a policy maps to. When catalog is empty (the GET /api/vars fetch
failed, or hasn't resolved), the dialog shows a one-line "unavailable"
notice instead of empty tables.
Var-legend reference dialog.
Sections: Request / Response / Message & consumer / Client — each built from
catalogentries with a non-emptypath, bucketed by the path's leading namespace segment (pathNamespace), with family entries (http_*,arg_*, ...) expanding into indented{{...}}sub-rows for every concrete membersuggestionsdiscovered once a trace snapshot is available (availability === 'ok') — see PathFamilyTable / pathFamilyMembers. Then Environment (names only, from theenvsuggestion group). Then a flat Legacy$varmapping table covering every catalog entry by its old name, for looking up what an existing$fooin a policy maps to. Whencatalogis empty (theGET /api/varsfetch failed, or hasn't resolved), the dialog shows a one-line "unavailable" notice instead of empty tables.