New theory on what might be causing this React error and failure to render in the browser. It is not the number of connections to a particular node (as mentioned above, 22 relationships is normally handled quite easily by the renderer), nor does it have anything to do with how numerous a particular node label is.
But rather it is due to NaN being in some of the property values. How did NaNs get in there? They got there via the BOLT protocol when I created the graph via Python from a large Pandas dataframe. In that dataframe, the 6 columns containing float datatypes have missing values, which are encoded as NaN by Pandas. So those NaN values are getting passed into the graph as is, since this is using BOLT. If using JavaScript or browser interface, these NaNs would have been converted to null as part of JSON-ifying the data. But I populated my graph's data using py2neo and BOLT connector.
Here is output from the cypher-shell for the problematic node ID of 10 that causing the React error:
neo4j> MATCH (n) WHERE id(n)=10 RETURN n;
+----------------------------------------------------------------------------------------------------------------------------+
| n |
+----------------------------------------------------------------------------------------------------------------------------+
| (:Label3 {item_id: "000000012345678", usage_type: "thing", z1: NaN, z2: NaN, y1: NaN, y2: NaN, x1: NaN, x2: NaN}) |
+----------------------------------------------------------------------------------------------------------------------------+
1 row available after 7 ms, consumed after another 0 ms
Thoughts? I'll see if I can use algo.isInfinite() from the graph algorithms plugin to clean the NaNs out of the graph.
What's odd is that, according to the screenshot posted here, at least at one point, the Neo4J browser was able to render nodes with NaN property values. Perhaps something changed with either the React library or the neo4j browser code..??