Skip to content

Schema watch mode #48

Closed
Closed

Description

@thomas-stegemann

Re-discover the active server URL(s) every N seconds and show a "+ added, − removed, ~ changed" delta in the sidebar.

Related

Tracked in ROADMAP.md — the narrative there carries the full design rationale + the per-bullet checkboxes. This issue exists for board-level Status / Area / Track / Milestone tracking.

Activity

  1. added this to the milestone on Jun 1, 2026
  2. moved this to Backlog in Bowireon Jun 2, 2026
  3. removed this from the milestone on Jun 6, 2026
  4. changed the issue type fromtoon Jun 7, 2026
  5. changed the issue type fromtoon Jun 7, 2026
  6. thomas-stegemann commented on Aug 3, 2026

    @thomas-stegemann
    MemberAuthor

    Verified end to end and closing.

    What was checked

    A fixture OpenAPI document served from a local HTTP server, swapped underneath a running watch so the poller saw a real change: /cranes added, /doomed removed, and listTugs keeping its name while its response shape gained two properties. That last one is the case worth having — a saved request survives syntactically and fails at runtime.

    All three delta kinds surfaced, in the sidebar, from one poll:

    where what it showed
    banner +1 method, −1 method, ~1 changed, naming the removed Fleet / GET /doomed
    service header chip +1 −1 ~1, with a per-kind tooltip
    method rows + on listCranes, ~ on listTugs

    Then reverted the schema and got the mirror image — /cranes reported removed, goingAway marked added, listTugs marked changed again. Console clean throughout.

    Two behaviours worth recording, because neither is obvious from the code

    A quiet poll does not clear the delta. It persists until dismissed. That is the right way round: clearing on the next poll would make a change visible for one interval and then vanish, so you would have to be looking at the right moment to ever see it.

    Dismissing clears all three surfaces at once — banner, chip and row marks — and leaves the watch running.

    Interaction with #551

    #551 stopped building method rows for collapsed services, so a row-level +/~ only exists once a group is expanded. The per-service chip is built for every service regardless, which is what keeps a change findable in a collapsed tree. Checked deliberately rather than assumed, because the row marks would otherwise have been silently unreachable for anyone with a large catalogue.

    What this issue does not cover

    The freeze investigated earlier in the v2.4 cycle was triggered by this poller but was never a property of it: the mechanisms found were unbounded observer accumulation (#550), an unbounded SSE reconnect loop (#552), and the render-path costs in #551. The first two are fixed and closed; #551 has one item still open (coalescing beyond the live-stream panels). The freeze itself was never reproduced under a profiler — that residual doubt belongs to those issues, not to this one, but it should not disappear just because this closes.

    Covered by 24 unit tests in schema-watch.test.mjs; full JS suite green at 446.

  7. moved this from Backlog to Done in Bowireon Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions