FLUID-5118: IoC expansion of distributed options is based on current component, rather than the one the options are distributed too

Metadata

Source
FLUID-5118
Type
Bug
Priority
Major
Status
Closed
Resolution
Not A Bug
Assignee
Antranig Basman
Reporter
Justin Obara
Created
2013-08-19T13:11:19.937-0400
Updated
2014-03-03T11:29:23.387-0500
Versions
N/A
Fixed Versions
N/A
Component
  1. IoC System

Description

When using distributed options, the IoC expansion seems to occur before the distribution of the options. The means that the resolution of {that} is based off of the existing component instead of the one to which the options are being distributed too.

This can be quite confusing, particularly for integrators who assume they are working with the options structure for the child component.

Comments

  • Justin Obara commented 2013-08-19T13:16:14.415-0400

    Issued a pull request ( https://github.com/fluid-project/infusion/pull/392 ) containing a test case demonstrating the issue.

  • Antranig Basman commented 2013-08-19T15:41:38.483-0400

    Hi Justin - this behaviour is just as designed, and it took some effort to get it that way! Options are always expanded based on the site of configuration and not the target component. This is because it is the original requester whose environment is relevant to configuration he provides. He cannot be expected to anticipate the destination site, and hence adjust his configuration for an unforseeable target - they may even be multiple such targets.