Fixed
Details
Assignee
Antranig BasmanAntranig BasmanReporter
Antranig BasmanAntranig BasmanComponents
Affects versions
Priority
Major
Details
Details
Assignee
Antranig Basman
Antranig BasmanReporter
Antranig Basman
Antranig BasmanComponents
Affects versions
Priority
Created February 9, 2017 at 2:22 AM
Updated February 9, 2017 at 3:33 PM
Resolved February 9, 2017 at 3:32 PM
An annoying edge case creates a bad interaction between fluid.construct and fluid.computeDistributionPriority -> fluid.getMemberNames.
If there is a global distribution which is capable of hitting components which are directly attached to the root, e.g.
using fluid.construct, say, with a path of "sample-model-component-0" to construct a component directly attached to the root will trigger a failure
since we don't handle the case where the path stack is empty. fluid.getMemberNames is pretty suspect anyway and has been ripe for fencepost errors for many years: