Skip to content

Initiative: Neighbor expansion enhancements #457

Open
0 of 16 issues completed
Open

Description

@kmcginnes

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

Choose the grain

Stay oriented

Feedback and correctness

RDF and SPARQL

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

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

  1. added
    enhancementNew feature or request
    explorationIssues related to graph exploration, node & edge details, neighbor expansion, etc
    usabilityIssues relating to the ease of use of the UI or features
    on Jul 9, 2025
  2. changed the title [-][Project] Neighbor expansion UX[/-] [+]Initiative: Neighbor expansion enhancements[/+] on Nov 18, 2026
  3. added
    internalSignals that the team will work on this issue internally.
    on Nov 18, 2026
  4. changed the issue type fromtoon Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestexplorationIssues related to graph exploration, node & edge details, neighbor expansion, etcinnovativeinternalSignals that the team will work on this issue internally.usabilityIssues relating to the ease of use of the UI or features

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions