You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optionally allow for "completing" the graph when the query does not contain edges between the nodes.
We could add a configuration that takes a list of relationship types or a wildcard (*) that, when specified will issue a second cypher query after the initial query has run to load the relationships between the nodes in the result set.
This helps when doing simple queries that only return nodes so that you get a connected graph (with the relationship types that you are interested in.
DataExplorer for Neo4j does this automatically and the neo4j browser has this option enabled by default.
Optionally allow for "completing" the graph when the query does not contain edges between the nodes.
We could add a configuration that takes a list of relationship types or a wildcard (*) that, when specified will issue a second cypher query after the initial query has run to load the relationships between the nodes in the result set.
This helps when doing simple queries that only return nodes so that you get a connected graph (with the relationship types that you are interested in.
DataExplorer for Neo4j does this automatically and the neo4j browser has this option enabled by default.
Proposed API:
This requires collecting the ids of the nodes and issueing the respective query to merge in relationships to the set of edges to pass to the widget.
The text was updated successfully, but these errors were encountered: