FLUID-4338: Context resolution with respect to member name fails to find components along direct that stack

Metadata

Source
FLUID-4338
Type
Bug
Priority
Blocker
Status
Closed
Resolution
Fixed
Assignee
Antranig Basman
Reporter
Cindy Li
Created
2011-07-12T17:35:18.005-0400
Updated
2013-04-11T17:08:53.740-0400
Versions
  1. 1.4
Fixed Versions
  1. 1.4
  2. 1.5
Component
  1. IoC System

Description

Although this name could be discovered by inspecting either the instantiator or the next supercomponent, visitComponents always supplies a member name of "" for every component on the direct path to root as a result of the line

if (visitor(that, "", options, 0, 0)) {

at line 69 of FluidIoC.js

Comments

  • Antranig Basman commented 2011-11-11T14:50:18.165-0500

    Not sure exactly how this was originally observed - since there is some tendency to be able to find such components through an exploration of the subcomponents of the parent - that is, to find them on the way DOWN even if you don't find them on the way up. However it was possible to construct a test case for this issue since finding them on the way down will trigger a circularity failure since they are not yet properly attached to the tree and so fail during ginger construction.

  • Antranig Basman commented 2013-02-01T04:16:27.802-0500

    Delivered for 1.4