Lakshay Saini 115e7965cd fix(explorer): gate temporal requests on graph load (#1003) ...

Explorer was firing temporal requests before the graph even loaded.

When the backend is down, /api/graph/nodes fails but the temporal
bounds and snapshot effects didn't care , they fired anyway, off in
their own corner, ignoring whether the graph actually came up. Every
page load with no backend meant three failed requests instead of one,
and a scrubber that had nothing to scrub.

Added two small predicate functions and gated the temporal effects on
them. Basically: don't ask for time-based data until you know the
graph itself loaded. An empty graph still counts as loaded, so that
case isn't broken.

Confirmed with the backend down, before and after: three failing
requests down to one.

Fixes #982.

2026-08-15 17:47:35 +05:00

..

graphSceneState.display.test.ts

fix(ui): resolve explorer redesign merge blockers

2026-05-16 15:55:47 +05:00

graphStore.multi-edge.test.mjs

feat(explorer): add Semantica Knowledge Explorer UI with full feature set

2026-04-13 13:40:40 +05:30

pluginRegistry.temporal.test.mjs

refactor: tighten comments across #830 changes for clarity

2026-08-05 17:52:21 +05:30

temporalLifecycle.test.ts

fix(explorer): gate temporal requests on graph load (#1003)

2026-08-15 17:47:35 +05:00