The /rover-planning index was rendering only band_mhz (the legacy primary single-band column), so multi-band missions with bands_mhz populated showed just the first band. Switched the renderer to arity-2 and now pulls the full bands list via Mission.bands/1, so multi-band missions render '10 GHz · 24 GHz · 47 GHz' etc. Sort still keys on band_mhz so the column stays sortable on a single scalar value. |
||
|---|---|---|
| .. | ||
| components | ||
| controllers | ||
| live | ||
| plugs | ||
| endpoint.ex | ||
| live_helpers.ex | ||
| live_table_footer.ex | ||
| live_table_resource.ex | ||
| location_resolver.ex | ||
| metrics_plug.ex | ||
| router.ex | ||
| skew_t.ex | ||
| telemetry.ex | ||
| user_auth.ex | ||