This is a relatively low-cost simple fix for gh-174, where we simply stop logging the "root" object. Users are still provided with information about which path segment failed, and this solves the issue of huge time delays spent in fluid.prettyPrintJSON for Flocking's (unfortunately) very circularly-referenced objects.
This is a relatively low-cost simple fix for gh-174, where we simply stop logging the "root" object. Users are still provided with information about which path segment failed, and this solves the issue of huge time delays spent in
fluid.prettyPrintJSONfor Flocking's (unfortunately) very circularly-referenced objects.