FlexMeasures / flexmeasures / 34280535465

86%

push

github

Status page: split sensor data and jobs into tabs (#2470)

* ui/status: split sensor data and jobs over two lazily-loaded tabs

Context:
- Issue #2446: the status page stacks the sensor connectivity table and
  the jobs table on one page, so every visit pays for both, even though a
  visitor is usually after one of them.

Change:
- Put each table in its own tab, and build a table only when its tab is
  first shown, so the page queries only what it displays.
- Open the jobs tab by default, and remember the tab the user last opened
  in their session, as we do for the preferred graph legend position.
- Add POST /api/v3_0/assets/status_page_tab to record that preference.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* tests: cover the status page tabs and the tab preference endpoint

Context:
- Issue #2446 splits the status page into a jobs tab and a sensor data tab,
  of which only the opened one loads.

Change:
- Assert that the status page opens the jobs tab by default, and the sensor
  data tab once the session records that preference.
- Assert that the new endpoint stores an accepted tab in the session, and
  rejects a tab the status page does not have.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* docs: add changelog entry for the status page tabs

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* ui/status: stop the tab tables opting into the global pagination helper

Context:
- With both tables built up front, the "paginate" class was harmless: the
  global initializer in flexmeasures.js found them already built and just
  handed back their API.
- Building a table only when its tab opens changed that. At page load the
  hidden table does not exist yet, so the global initializer created it with
  default options and no data source. Opening its tab could then no longer
  initialize it, DataTables refuses to reinitialize, and the swallowed error
  left an empty table behind until the page was reloaded.

Change:
- Drop th... (continued)

11 of 11 new or added lines in 1 file covered. (100.0%)

18476 of 21736 relevant lines covered (85.0%)

0.85 hits per line