FLUID-3818: IoC "value resolution" currently does not search the dynamic environment for resolving context names

Metadata

Source
FLUID-3818
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Justin Obara
Reporter
Antranig Basman
Created
2010-10-25T15:36:01.954-0400
Updated
2010-10-28T14:59:44.350-0400
Versions
  1. 1.2.1
Fixed Versions
  1. 1.3
Component
  1. IoC System

Description

Whilst names held in the dynamic environment are used for function resolution, at present only names in the "that stack" are used for value resolution. These forms of resolution should be made consistent

Comments

  • Justin Obara commented 2010-10-25T16:25:32.581-0400

    "Bug Parade Infusion 1.3"

  • Antranig Basman commented 2010-10-26T02:44:13.742-0400

    Fixed at revision 10158 - please review. NOTE that as a result of the remaining issues surrounding FLUID-3771, it is still not possible to apply this or any other value resolution to values which occur at top-level inside fluid.defaults (that is, not as either a demands block or the options for an IoC-driven subcomponent). This fix also removes what was once a helpful diagnostic on failing to match a context name within the "that stack" - the default behaviour on failing to match a name in the environment is simply to silently return an undefined value. This was found helpful in cases where we did "pure environmental resolution" (which we are now sharing code with via the new utility fluid.environmentFetcher) but perhaps we should reconsider whether it is appropriate here.

  • Michelle D'Souza commented 2010-10-28T14:59:44.348-0400

    The tests pass and the code looks reasonable.