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
kinship1 custom.json
This is a modified version of the original kinship 1 JSON file, which includes new key/value pairs to support customizing which nodes get expanded at the start, as well as the screen size.
The issue was that the kinship diagrams depended on an old version of d3-dag, which was throwing the errors when aggregated. The updated library came with many breaking changes, so this PR replaces the old functions with the new ones, as well as factoring out the hard coded values into the JSON files instead.
The main issues were
Deprecated functions, especially those that returned an array - now returns a generator and is now manually converted into an array
Old code referenced a children property of all_nodes but this resulted in conflicts with the library as it does not expect our custom children property, so that was renamed
Hard coded values for certain diagrams to display certain nodes at the start and setting the screen size based on them, which has be removed in favour of setting these values in the JSON file instead
When updating the library, the initial screen position, and where the screen/zoom would go after clicking on a node was broken, so added code which seems to put the screen around the node consistently
The old code used .coordVert() but this was replaced by .coordQuad(). However, that resulted in about ~20s load times so switched to .coordGreedy() instead
Visit
/admin/config/development/performance
, make sure these 2 options is enable.Visit the node which has the data visualization field formatter is used. the diagram are not rendered.
Right click on the web page, there is this error:
This field formatter can be found at:
if there is an JS error $.once is not a function, install this module: https://www.drupal.org/project/jquery_once
The text was updated successfully, but these errors were encountered: