aws/graph-explorer

Description When expanding a node's neighbors with attribute filters, if the filters match nothing, the app shows the toast "No more neighbors to expand" — which implies the node is fully expanded. The truth is the opposite: the node has neighbors, but the applied filters excluded all of them. A user would reasonably conclude there is nothing left and stop, when relaxing the filter would reveal neighbors. This is connector-agnostic — the toast lives in the shared expand hook (useExpandNode), so it affects Gremlin, openCypher, and SPARQL alike. Environment OS: N/A Browser: N/A Graph Explorer Version: current main Graph Database & Version: any (Gremlin / openCypher / SPARQL) Steps to Reproduce Open the expand-neighbors sidebar for a node that has neighbors. Add an attribute filter whose value matches none of them (e.g. a value no neighbor's property contains). Expand. See the toast "No more neighbors to expand". Expected Behavior When the expansion request carried attribute filte

Description When the database or proxy returns a 403 Forbidden, the user sees the generic Network Response 403 title with whatever raw message the server returns, which is often an opaque JSON blob or empty. There is no dedicated branch in createDisplayError for 403, so it falls through to the catch-all NetworkError path. A 403 can be caused by several things (credentials, permissions, proxy configuration), so the message should stay generic and point the user at what they can reasonably check. Environment All environments, browser-based Steps to Reproduce Connect to a database or proxy that will reject requests with 403 Trigger any request (e.g. schema sync) Expected Behavior A friendly, generic message such as: Access denied The server refused this request. Check that your connection credentials and permissions are correct, then try again. Actual Behavior Title says "Network Response 403" and the message is either the raw server response or the generic "An error occurred. Pleas

Description When a blank node (bnode) with no type is rendered on the graph canvas, it has no icon. However, when the same node is selected, the details/properties panel shows the default icon. The icon display should be consistent between the two views. The root cause is that the canvas icon rendering path (useBackgroundImageMap) only creates Cytoscape style selectors for vertex types that exist in the schema. Since "«No Type»" is a synthetic label assigned at runtime (vertex.ts:80-83) and isn't in the schema, no icon style is generated. The details panel uses useVertexPreferences() which always falls back to DEFAULT_ICON_URL regardless of schema presence. Relevant code paths Canvas: useGraphStyles → useBackgroundImageMap → renderNode (skips types not in schema) Panel: VertexIcon → useVertexPreferences → always returns defaultVertexPreferences.iconUrl Environment Graph Database & Version: Any SPARQL endpoint with blank nodes Steps to Reproduce Load a graph containing a

When the user right clicks on the graph canvas, they should have a few options to select various items in the graph. Select all nodes Select all edges Select all This would replace whatever is already selected.