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
The current API makes it easy to style nodes/relationships based on their label/type.
This approach falls short when trying to style items across labels/type (and maybe only some of those labels/items). Think about a path that crosses single nodes/relationships of different types. There is no easy way to highlight this path then.
Which is then applied to the set of nodes (same for relationships).
Not sure if the query approach would work well here. We would need to make sure to only query nodes that are already in the result of show_cypher, or would it be a good idea to potentially run the query against the entire database and just load those items as well?
The text was updated successfully, but these errors were encountered:
I guess this could be done with some cypher magic, where you "embed" that information into the query result.
It should be possible to yield nodes that have "properties" which are computed, live. Just like it is possible to create virtual nodes and relationships.
I don't like adding a cypher query as configuration. We could however let the user modify the data, before it gets visualized. So instead of passing in a query, allow the user to pass in a neo4j graph (or graph-like object) and then just modify the values in memory before visualizing them?
The current API makes it easy to style nodes/relationships based on their label/type.
This approach falls short when trying to style items across labels/type (and maybe only some of those labels/items). Think about a path that crosses single nodes/relationships of different types. There is no easy way to highlight this path then.
Maybe we could add something like
Which is then applied to the set of nodes (same for relationships).
Not sure if the query approach would work well here. We would need to make sure to only query nodes that are already in the result of
show_cypher
, or would it be a good idea to potentially run the query against the entire database and just load those items as well?The text was updated successfully, but these errors were encountered: