thebestnom
commented
4 years ago Currently it takes the first label (I don't really know what this means 😅), it's kinda arbitrary... We need to implement multi labels for a lot of time, but I didn't had the energy to bug the maintainer again (It's kinda hard to reach him) for everytime I want to merge something so I just kinda gave up...
If you want to implement it, it shouldn't be that hard, and I can get in contact with him after you open pr
Scenario -
Database tables interacting with each other (within same and different databases)
Setup -
Nodes have label = "SourceTable", "TargetTable".
both these type of nodes also share a label called "Table".
all nodes have been pageranked and community identified.
the relationship between them is - (t:Table)-[:INTERACTS_WITH]->(t1:Table)
nodesize has been set to pagerank and color has been set to community
Query: match (t:Table)-[r:INTERACTS_WITH]->(t1:Table) return t,r,t1 limit 400
instead of getting the social graph, this is what I get -
Question - how exactly does neovis pick the default label to display? In the style settings, I've clearly asked it to pick the "Table" label and display the property - tableName which is shared by both Sourcetable and TargetTable.
("SourceTable" and "TargetTable" as displayed in the image are not node properties if anyone is wondering about that!)
Even this isn't an issue if node size was being properly reflected as per the pagerank values. As you can see, relationship thickness is the only thing that being correctly rendered here.