Skip to content

fix: topology graph empty after async fetch #113

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
reloadfast merged 1 commit into from
Mar 2, 2026
Merged

fix: topology graph empty after async fetch #113

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 11 additions & 8 deletions frontend/src/pages/TopologyPage.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,16 +210,19 @@ export function TopologyPage() {
[topology, gateway],
);

const [rfNodes, , onNodesChange] = useNodesState(initialNodes);
const [rfEdges, , onEdgesChange] = useEdgesState(initialEdges);
const [rfNodes, setNodes, onNodesChange] = useNodesState(initialNodes);
const [rfEdges, setEdges, onEdgesChange] = useEdgesState(initialEdges);

// Sync when topology loads
const [synced, setSynced] = useState(false);
// Sync React Flow state when topology data arrives (useNodesState/useEdgesState
// only consume their argument as an initial value, so async fetch results must
// be pushed in explicitly via setNodes/setEdges).
useEffect(() => {
if (topology.length > 0 && !synced) {
setSynced(true);
}
}, [topology, synced]);
setNodes(initialNodes);
}, [initialNodes, setNodes]);

useEffect(() => {
setEdges(initialEdges);
}, [initialEdges, setEdges]);

if (loading) {
return (
Expand Down
Loading