Repository navigation
v2.206.0
The DataPath table renders when a lane is kept in another NAD Block
v2.202.0 added a dropdown entry that keeps a lane staged in another NAD Block. That entry used two names, bankOf and appName, which were declared further down the same function. On the first such lane the browser threw "Cannot access 'bankOf' before initialization" and the whole DataPath table showed nothing. It happened on exactly the modules the entry was written for. The earlier tests read app.js as text, which cannot show declaration order. Walking the tab in the browser on the 24-lane demo with Block 1 staged is what exposed it.
Now
- Both names are declared before the dropdown is built. Lane 1 shows "AN 16 (NAD Block 1, AppSel 1) — kept" with its media lanes and "running App 1".
- The page's loaders are run for real in the tests. app.js is loaded into Node under a catch-all DOM, and every GET is answered with the server's own reply for that path.
- Each loader runs against every demo module, against a lane kept in another NAD Block, and against a Network Path Application. A loader that throws is a panel that does not render. A self-test checks that the harness does catch one.
2955 end-to-end tests. 32-bit build, as CH341 requires.