aws/graph-explorer

Restoring previous graph leaves restore button present

Open

#959 opened on Jun 5, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (456 stars) (88 forks)auto 404
good first issuequery editor

Description

Steps to reproduce

  1. Add a node to the database using query editor g.addV()
  2. Add new nodes to graph visualization
  3. Drop new node from database g.V('{id}').drop()
  4. Refresh browser
  5. Click restore previous graph button

Expected results

No nodes should be added to the graph, but the restore button should disappear. Also, a warning/soft error should be shown letting the user know that a node could not be found.

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitJavaScriptTypeScriptReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Investigate the restore graph functionality. Look at the component that handles the restore button, trace how it checks for existing nodes, and ensure it properly handles cases where nodes are missing. Add a warning message when nodes cannot be found.