Repository navigation
Description
Initiative: a body of work too big for one release, expressing a vision. A never-tracked container; the board tracks its children.
Vision
Make neighbor expansion the fastest way to explore a graph. Users see what's connected before they expand, choose what to bring in at the grain that fits the moment, and keep their bearings as the graph grows.
Goals
- See before expanding. Show which neighbors, node types, and edge types a node has, with counts and how many are already in the graph.
- Choose the grain. Expand one neighbor, a whole node type, a whole edge type, or a filtered set.
- Expand from where you are. Start an expansion from the node, the context menu, the sidebar, or the table, without hunting for hidden options.
- Stay oriented. Expanding adds to the graph without rearranging what's already there or moving the view more than needed.
- Clear, correct feedback. Limits are respected, and messages say what actually happened.
- Every query language. Gremlin, openCypher, and SPARQL, including RDF-specific cases.
Sub-issues
See before expanding
- [Feature Request] Show list of neighbors, node types and edge types in expand sidebar #647
- Show neighbors for selected node in table view #1334
Choose the grain
- Change Expand Relationships Windows #2143
- [Feature Request] Add ID to the filter drop down for neighbor expansion #274
- Expand neighbors by type from the node and the context menu #2640
- Let users choose how many neighbor types show before "Show more" #2642
Stay oriented
- Keep the graph steady when expanding neighbors #2641
- Add ability to disable fit to frame on expansion #898
- [Usability] Removing a central node does not remove the neighbors #96
Feedback and correctness
- Misleading "No more neighbors to expand" message when filters exclude all neighbors #2060
- "Error updating neighbor counts" toast appears when the request was only cancelled #2385
- [Bug] Value in "Limit returned neighbors to" is exceeded (SPARQL ENDPOINT) #184
- Blank nodes returned during expansion are not being recognized #1404
RDF and SPARQL
- [Feature Request] Allow expansion of RDF classes #135
- Allow expanding of BNode->edge->BNode relationships #19
- [Feature Request] Expand RDF triples as separate nodes and edges #215
Scoping
Not yet charted. When a release picks up part of this initiative, it takes a slice of the sub-issues as a phase. The default expansion limit from the original task list shipped as a per-connection setting in 3.3.0.
Related Issues
- Related to Graph Layout Enhancements #2017
- Related to [Roadmap] Improved Graph Rendering #691
Important
Internal only — this issue is maintained by the core team and is not accepting external contributions.
🤖 Written by an AI agent on my behalf.
Activity
[-][Project] Neighbor expansion UX[/-][+]Initiative: Neighbor expansion enhancements[/+]